Maybe the biggest difference between Ada and true Wirth languages is that it is not deliberately minimal.
Would you say that Ada sits close to Modula 2 philosophically, but industrial-scale?
Ada is in every aspect a much bigger and more powerful (e.g. concerning the ability of the compiler to assist you in writing safe low-level code) language than any of the Wirth languages. Wirth famously criticized Ada as being "uneconomical"; he believed that because Ada’s requirements were so "baroque" and contradictory, the resulting language was inevitably overloaded with features whose marginal benefits did not justify their complexity (https://archive.org/details/Computer_Language_Issue_09_1985-...). But when you e.g. study the Oberon system, you see that it depended on "tricks" (e.g. SYSTEM.PUT/GET, VAR ARRAY of SYSTEM.BYTE) which were not properly integrated in the language concepts and had to be used without any typechecking support by the compiler.
In the Rationale for the Design of the Ada Programming Language (published as SIGPLAN Notices, June 1979), the design team explicitly lists their influences. Mesa (a language developed at Xerox PARC, where Wirth made his sabbaticals) is cited as a source for the module/package concept. Modula (referring to Modula-1, 1977) is cited in the context of concurrency and low-level hardware access (e.g., handling interrupts, device drivers), and for the general concept of the module as a syntactic unit. From the timeline we can assume that Modula-2 had not arrived at the design team when they released their proposal to the DoD. Notably, Wirth had actually submitted his own proposal to the DoD (the "Yellow" language, via SRI in 1977), though he withdrew it early because he felt the requirements were too complex. Unfortunately, no public specification of the "Yellow" language exists, but it was very likely not Modula-2.