Yes, our Northrop ATA had a wider wingspan, was slightly larger but we proposed OTS F404 engines as compared to the A-12 but we tried to convince the USN that to attack using an LO aircraft, you have to do it from medium to high altitudes, this is from vast experience on other programs. A flying wing on the the deck, a sitting duck. So our bid was unresponsive since the FFP contract had loads of risk and the USN kept jacking around with the spec, that my friends is what kills programs. And CTR you are correct, if anyone has a chance to read the $5 Billion Dollar Misunderstanding, is good reading but a bit heavy on the politics and financials but a very good book overall.
Did the lessons Grumman learned from the fixed-price contract in the F-14 program influence the Northrop/Grumman team's decision to reject a fixed-price contract from the Navy for the ATA program?
That would be a very difficult canopy to fabricate plus it has to survive testing.
Was the YF-23's canopy design also due to the difficulty of manufacturing a large, one-piece canopy, leading to the choice of a conventional two-piece design? Considering the F-22, F-35, and even China's J-20 and J-35, which all use one-piece canopy designs, can a non-one-piece canopy design still meet LO requirements?
 
Did the lessons Grumman learned from the fixed-price contract in the F-14 program influence the Northrop/Grumman team's decision to reject a fixed-price contract from the Navy for the ATA program?

Was the YF-23's canopy design also due to the difficulty of manufacturing a large, one-piece canopy, leading to the choice of a conventional two-piece design? Considering the F-22, F-35, and even China's J-20 and J-35, which all use one-piece canopy designs, can a non-one-piece canopy design still meet LO requirements?
We had a hard time with TSSAM, tri-service and a fixed-price contract, at least JSF/F-35 pulled off the tri-service part.
 
That would be a very difficult canopy to fabricate plus it has to survive testing.

I'm still confused about how the polycarbonate transparencies are secured. Judging from the first photo, I assumed the transparencies were mounted on the exterior side of the support frames. But the second photoraises a question for me, where metallic strips that fasten the outer face of the transparencies to the support frames are plainly visible. Moreover, these strips appear to lie flush with the transparencies. This differs from the canopies of the F-15 and F/A-18, where the support frames protrude slightly above the transparencies.

Finally, will all seams be treated to make them invisible or optimize RCS?
The the forward most transparency was over 1 inch thick, the center transparency was thinner to save weight which was possible because the stresses were lower, but it was still about 3/4 an inch thick. I don’t recall if we thinned the aft most transparency further or it was the same as the center.

The frames allowed us to step down the thickness to save weight. We looked at if we could have one transparency with a smooth outside surface and reduce the thickness internally in steps to save weight, but this was not possible to manufacture and maintain adequate optical properties.

The stress risers from bolted joints on transparencies are the weak point for bird strike stresses. On conventional aircraft like the F-15 and F/A-18, to permit a thinner transparency to save weight the lower sill edges fit into channels and fastened with thru bolts. Because the joint is not in high tension, the canopy bow frames are often a bonded joint in the channel without bolts. Not having any bolts on the bow frames is the ideal joint if loads from cockpit pressure permit.

On the A-12 transparencies, they were so thick to maintain the LO required contour under cockpit pressure it was not necessary to use the typical channel joint. The transparencies were bolted on top of the frames and the transparency edges had bonded on Kevlar/Fiberglass strips inside and out along with compliant bushings in the holes.

To provide an acceptable LO surface the joints between transparencies, the edges were slightly tapered similar to drywall joints. Is allowed application of tape and a putty like compound to be applied to maintain a smooth service. I actually won a trip out to the pole test site to run tests on different transparency joint configurations and compounds.
 
Last edited:
Did the lessons Grumman learned from the fixed-price contract in the F-14 program influence the Northrop/Grumman team's decision to reject a fixed-price contract from the Navy for the ATA program?

Was the YF-23's canopy design also due to the difficulty of manufacturing a large, one-piece canopy, leading to the choice of a conventional two-piece design? Considering the F-22, F-35, and even China's J-20 and J-35, which all use one-piece canopy designs, can a non-one-piece canopy design still meet LO requirements?
The ATF and ATA development aircraft canopies were not designed or manufactured to achieve production aircraft LO requirements. Additionally, for the X-32 and X-35 having a separate thicker windshield for bird strike allowed for a thin stretched acrylic canopy transparency over the pilot to punch through without jettisoning the canopy. This reduced development schedule and cost, plus eliminated the ejection time delay of waiting for the canopy to fully clear the seat trajectory. For VTOL aircraft configurations minimum escape system time is critical. Note the installation of MDC on both ATF development aircraft canopies. FYI. The X-32 reused the AV-8B Harrier windshield and canopy.
 
Last edited:
The ATF and ATA development aircraft canopies were not designed or manufactured to achieve production aircraft LO requirements. Additionally, for the YF-34 and YF-35 having a separate thicker windshield for bird strike allowed for a thin stretched acrylic canopy transparency over the pilot to punch through without jettisoning the canopy. This reduced development schedule and cost, plus eliminated the ejection time delay of waiting for the canopy to fully clear the seat trajectory. For VTOL aircraft configurations minimum escape system time is critical. Note the installation of MDC on both ATF development aircraft canopies. FYI. The YF-34 reused the AV-8B Harrier windshield and canopy.
BTW, I believe you mean X-32 and X-35. Just saying. ;)
 
BTW, I believe you mean X-32 and X-35. Just saying. ;)
Thanks, having new carpet put in the house and I’ve been working too many hours moving furniture to type straight. Just edited it correct.
 
Did the lessons Grumman learned from the fixed-price contract in the F-14 program influence the Northrop/Grumman team's decision to reject a fixed-price contract from the Navy for the ATA program?

Was the YF-23's canopy design also due to the difficulty of manufacturing a large, one-piece canopy, leading to the choice of a conventional two-piece design? Considering the F-22, F-35, and even China's J-20 and J-35, which all use one-piece canopy designs, can a non-one-piece canopy design still meet LO requirements?
The YF-23/F-23 even though was not a single piece did meet all LO requirements.
 
The YF-23/F-23 even though was not a single piece did meet all LO requirements.
I concur that the YF-23 demonstrator and supporting documentation were compliant to the contract specifications. However ATF submissions permitted final production aircraft performance to be supported by analysis and for LO requirements, element and full scale model testing.

I know from supporting the F-22 canopy actuation specifications as a supplier for the production F-22 that the YF-22 never addressed the non planform aligned seam between the fixed windshields and opening canopy bow frames. I had assumed this was true also for the YF-23.

How did the YF-23 address the bow frame seam issue to meet LO requirements?
 
Last edited:
Just like B-2 with it's non-aligned windows frame. Conductive putty seal etc.
The B-2 windows don’t open for crew entry. And I don’t believe it’s practical to putty in the pilots every time you close a canopy. ;)
 
Blade seals. And F-23 EMD canopy frame is angled to all primary axes. Just like with fuselage service panels with exposed aligned edges I don't see unsolvable problems for delivering low RCS.
 
Last edited:
Blade seals will work on applications like landing gear and weapons bay doors, and then they are planform aligned. To remain adequately compliant blade seals must be designed relatively flat and without tight curvature. So no, based on my experience, blade seals are not suitable for this application. Believe me I have tried.

Opening canopies are giant bimetallic strips which bend up when cold and down when hot to the differential thermal expansion between the transparency material and their frames. Additionally canopys react cockpit pressure loads, which are pushing it away from the windshield. Finally, climbing across a blade seal when entering a cockpit risks, both injury to the pilot and damage to the seal.

These are the reasons that drove the large single piece assembly of three transparencies configuration canopy on the A-12. For pilot ingress egress the canopy needs to open to the side due to ceiling clearance in the hanger bay. To jettison, the A-12 canopy has hinges in the back similar to an F/A-18. Had we been able to solve the canopy bow frame LO issue we could had incorporated a conventional opening canopy like on an F/A-18. Instead, we needed to design the equivalent of a two-way station wagon tailgate.
 

Attachments

  • IMG_0487.jpeg
    IMG_0487.jpeg
    208.9 KB · Views: 169
  • IMG_0488.jpeg
    IMG_0488.jpeg
    81.9 KB · Views: 120
  • IMG_0490.jpeg
    IMG_0490.jpeg
    733.3 KB · Views: 103
  • IMG_0489.jpeg
    IMG_0489.jpeg
    130.5 KB · Views: 137
Last edited:
Thanks for the historical ATA detail. I offer one ATF clarification from firsthand knowledge:
  • Actual F-22A takeoff gross weight (TOGW) for the design missions (Mission 1, all subsonic; Mission 2, mixed sub/supersonic) were both a bit over 64,000 lb.
  • The design TOGW in the EMD proposal was 57,300 lb. During EMD, GDFW often complained (even in front of Gen. Fain) that the Lockheed proposed weights were way off and unachievable. [this public display of insubordination later was a factor in the Lockheed purchase of GDFW ... more someday on this ...]
  • The F-22A max TOGW of 85,000 lb was for Mission 3 (an all-subsonic one-way ferry mission employing (4) 600-gal external tanks and carrying a ferry load of internal and external AIM-120 weapons). The EMD proposal number for max TOGW was above 80,000 lb, but I don't have a more exact recollection.
Did F-22 EMD proposal have the same fuel and payload as actual F-22A? If so that is quite massive empty weight increase of about 6,700lbs? If so, using Breguet range equation for approximation, and assuming same internal fuel, that is over 12% range loss.

You then mention internal fuel capacity increase in EMD, is this the fin and saddle tank discussed in some sources, like Miller 2005? I believe in 1995 reporting was F119 missed subsonic TSFC by 8% while HPT redesign eventually allowed it to get within 2%.
https://web.archive.org/web/2026040...xed-wing/1995/05/f-22-weight-increase-agreed/
 
After reading through the almost 20 years of A-12 Avenger posts on Secret Projects, I was disappointed to find only posts from individuals never directly on the MD/GD team (please correct me if I am in error). Additionally, the few posts by individuals that worked for Northrup or Lockheed are equivalent to a few small puzzle pieces from a ten thousand piece picture puzzle. One cannot realistically know from a few puzzle pieces of the sky if a picture puzzle is of a tree or a ship. Especially when individuals more interested in their government careers than exposing the truth dump additional puzzle pieces in the box that don't belong.

Think about it, how could the two companies that designed and built the F-15 Eagle and F-16 Fighting Falcon fail so badly?
As I recall they took 5th and 3rd place respectively in the previous ATF competition. Unless they'd been flying something in secret, this was their first stealth aircraft. That's bound to have a hell of a learning curve.
 
The YF-22 had quite a bit more fuel IIRC. ~22k to 18k for the production version. The back end got a lot slimmer.
YF-22 wasn’t EMD F-22 proposal, it predated by a few years so that it could be built and flown by time EMD proposal was submitted. Actual EMD proposal (Config 637 or 638) outer lines are near identical to actual F-22A (Config 645) but not the internal structure it seems which saw a lot of revisions as @timmyjohn has talked about.

The US Airforce was downright pissed when they read the MD ATF RFP response in 1986. Out of either arrogance or honesty MD told the Airforce SPO that it was not possible to build an ATF with the specified performance, weight, and estimated production cost in the RFP. So MD submitted proposals for multiple different aircraft designs, with no one design promising to meet all the RFP requirements.
…
But the US Navy told MD and GD that they had used data from on F-117 and B-2 programs to develop their aircraft weight estimates (including the weight of necessary RAM). This was a lie, and by government regulation invalidated the contract.
Was the noncompliance mainly in the LO? As mentioned McDonnell Douglas had hired Alan Weichmann due to lacking prior experience and according to some accounts was elevated in response to poor performance on ATF proposal.

Did government not own the IP for RAM and other LO data for the F-117 and B-2? Because otherwise the USN should have been able to furnish that to contractors for the ATA?
 
Last edited:
YF-22 wasn’t EMD F-22 proposal, it predated by a few years so that it could be built and flown by time EMD proposal was submitted. Actual proposal outer lines are near identical to actual F-22A but not the internal structure it seems which saw a lot of revisions as @timmyjohn has talked about.
The YF-22, that flew, is very different than the F-22A. I think you are saying that the YF-22 that they flew is not the same as what they proposed? :confused:
 
The YF-22, that flew, is very different than the F-22A. I think you are saying that the YF-22 that they flew is not the same as what they proposed? :confused:
Yes and it makes sense. F-22 EMD proposal was submit by December 1990 but actual YF-22 has to fly well before then, so naturally it needed to come before so it could be built and flown first before submitting EMD proposal.
https://www.secretprojects.co.uk/threads/who-is-the-designer-of-f-22-raptor.44044/#post-700599
https://www.secretprojects.co.uk/th...lation-and-theories.45737/page-19#post-770687
 
Was the noncompliance mainly in the LO? As mentioned McDonnell Douglas had hired Alan Weichmann due to lacking prior experience and according to some accounts was elevated in response to poor performance on ATF proposal.

Did government not own the IP for RAM and other LO data for the F-117 and B-2? Because otherwise the USN should have been able to furnish that to contractors for the ATA?
The noncompliances used for termination for cause by the US government were cost schedule and weight. LO was never listed as a primary consideration for terminationin any of the information published.

Technically, the government owned the IP used for the F117 and the B-2. The information however was in the possession of Lockheed and Northrop. Release of any of this data had to be funneled through the US Air Force. None of these parties had any desire to share the information.
 
Did F-22 EMD proposal have the same fuel and payload as actual F-22A? If so that is quite massive empty weight increase of about 6,700lbs? If so, using Breguet range equation for approximation, and assuming same internal fuel, that is over 12% range loss.

You then mention internal fuel capacity increase in EMD, is this the fin and saddle tank discussed in some sources, like Miller 2005? I believe in 1995 reporting was F119 missed subsonic TSFC by 8% while HPT redesign eventually allowed it to get within 2%.
https://web.archive.org/web/2026040...xed-wing/1995/05/f-22-weight-increase-agreed/
The archived flightglobal.com article accurately states the weight status at that time, and is correct that the all-subsonic Mission 1 radius and the transonic sustained-g threshold were the performance specs that were driving the team-wide weight control program.

The F-22A proposal design takeoff weight (for Mission 2) was 57,300 lbs, which eventually grew to about 64,000 lbs at the time of the 3rd vehicle's first flight (4003 with full avionics suite). By payload, if you mean weapons, same as proposal. Avionics/sensors, very little increase. Other fixed weight items (utilities, subsystems, RAM/RAS, etc.) some increase. The airframe structure itself experienced the largest weight increase from the proposal. The fuel loads did need to increase beyond the proposal values: for Mission 2 due to the weight-empty growth, for Mission 1 due to the F119 out-of-spec subsonic SFC and the weight-empty growth.

I can't provide quotable numbers for the internal fuel load increase, nor for the overall weight-empty increase, mainly because it's been 3 decades. The tail fin root tanks and saddle tanks (and a wedge tank behind the nose gear) were volumes that were 'reserved' for future use if the Air Force decided to not provide a bit of relief on the Mission 1 radius or the transonic sustained-g maneuver point (which they did, however the changes were quite small).

I can't speak to any engineering changes that happened after first flight.

Sidenote: use of the Breguet range equation is ill-advised outside of a junior-year aircraft design class. Mission radius calculations, and the tables of aerodynamic and propulsion input data, are much more complicated than that.

Finally, why was the actual design TOGW about 12% higher than the proposal? (which is not unusual historically with state-of-the-art designs.) In my mind, there are four principal reasons, in no particular order:
  1. Three-way teaming: the $800M+ investment for ATF's pre-EMD phases necessitated a teaming arrangement. Because the F-22A proposal configuration lacked commonality with the YF-22 flight demonstrator, the aircraft design was sliced into thirds while relatively immature. During EMD this led to a lot of sub-optimization in Fort Worth, Seattle, and Marietta. Co-located weight control drills notwithstanding.
  2. Very sImilar to the A-12 program, GDFW showed a tendency to design the F-22A mid-fuselage composite parts with a "black aluminum" mindset. Meanwhile Boeing failed to successfully engineer their ambitious wing concept featuring thermoplastic sine-wave spars, plus their inexperience with large titanium structure led to weight and producibility problems with the aft fuselage.
  3. The P&W F119 subsonic SFC spec exceedance.
  4. (Now for Lockheed) The proposal weight for the F-22A relied to large degree on the in-house aircraft sizing tool known as ASSET (Advanced System Synthesis and Evaluation Technique). ASSET was developed in the 1970s for transport-type aircraft. I've been told that tweaks were made to reflect fighter/attack aircraft in the late 70s (Senior Trend) and early 80s (ATF). In the early 90s, I heard GDFW personnel grumble about ASSET's lack of agreement with their own sizing and parametric weight methods, as the team-wide weight-control pressure mounted.
 
Last edited:
Interesting, all this makes one wonder if Northrop/McDonnell Douglas would have experienced as much weight growth on the ATF, and also if Northrop/Grumman ATA weights were realistic.

Thanks for this. I had always heard that MAC had one of the best weights groups in the business and I figured they probably accurately predicted what the ATF was going to weigh and were penalized for it. Although, I understand they were still lacking in L.O. tech, which is why they hired Alan Wiechman.
On this note, what was the reputation for Northrop or Grumman for predicting weights?

As for Lockheed, ironically one thing I heard about Kelly Johnson is that he’s excellent at estimating aircraft weight, often just by looking at it.
 
Interesting, all this makes one wonder if Northrop/McDonnell Douglas would have experienced as much weight growth on the ATF, and also if Northrop/Grumman ATA weights were realistic.


On this note, what was the reputation for Northrop or Grumman for predicting weights?

As for Lockheed, ironically one thing I heard about Kelly Johnson is that he’s excellent at estimating aircraft weight, often just by looking at it.
IMHO, I believe all of the major legacy aircraft manufacturers are an order of magnitude better at estimating final aircraft weights, than the USAF and USN are at specifying not to exceed weights.
 
Last edited:
Interesting, all this makes one wonder if Northrop/McDonnell Douglas would have experienced as much weight growth on the ATF, and also if Northrop/Grumman ATA weights were realistic.

On this note, what was the reputation for Northrop or Grumman for predicting weights?
Thanks for teeing up another one. Yep, I worked X-29 in the pre-FSED days, and since that's the only new Grumman aircraft since the F-14A, it's an ideal case of gauging how well the (relatively small) team was able to predict the weight of a unconventional design with a few state-of-the-art features.

A bit of background. A source of pride within the Advanced Design organization was the homegrown parametric sizing tool, known as WISE (Weight Integrated Sizing Evaluation). In fact, during the early ATF studies (1976-1981) one of the few attaboys that the Air Force Flight Dynamics Lab (AFFDL) engineers in Dayton often passed on to Grumman was how thorough and believable the parametric-based weight estimates appeared, as compared to the 'competition'...

The X-29 design was initially drawn in late 1977, and the configuration was sized with the following weight values:
TOGW = 16.000 lb. Fuel wt = 4,000 lb. Maneuver Design wt = 14,000 lb (50% fuel).

With the 185 sqft forward swept wing, the intended lift coefficient at the FSW design point (4.5-g sustained, Mach 0.9, 30Kft altitude) was: CL = (4.5*14,000)/(356*185) = 0.955

Fast forward to the Dec. 1984 first flight, the X-29 actual weight values were:
TOGW = 17,700 lb. Fuel wt = 3,978 lb. Maneuver wt @50% fuel = 15,710 lb.

The actual TOGW was a bit more than 10% higher than the initial parametric estimate. I'll leave it to the audience to decide how good or bad a prediction this was.

Relative to the Northrop/Grumman/Vought ATA effort, I'll add that Grumman-Bethpage sent absolutely their first-string team to Northrop-Pico Rivera (nope, I wasn't picked). One of the Grumman technical leaders told me that he was under the impression that "Northrop has the C-team on the program" -- which in hindsight makes sense: ATB/B-2 first string; ATF/F-23 second string; ATA third string.
 
The actual TOGW was a bit more than 10% higher than the initial parametric estimate. I'll leave it to the audience to decide how good or bad a prediction this was.
I'm going to say "not unreasonably off, and probably would have been better if Grumman had better information on how heavy the wing ended up." Even with composites and exotic layup methods to turn the normal FSW wingtip-AoA-increasing twist into a spanwise flex.

But I'm just a tin banger, not an edumacated engineer.
 
The actual TOGW was a bit more than 10% higher than the initial parametric estimate. I'll leave it to the audience to decide how good or bad a prediction this was.
Pretty typical and quite a bit worse than some parametric methods.

A key thing with development of these parametric weights methods is the database of real aircraft behind them in number and variety, to then properly tease out correct regression lines.

But they are also simplistic methods, you still need to bear in mind the physics underneath when applying.
 
Thanks for teeing up another one. Yep, I worked X-29 in the pre-FSED days, and since that's the only new Grumman aircraft since the F-14A, it's an ideal case of gauging how well the (relatively small) team was able to predict the weight of a unconventional design with a few state-of-the-art features.

A bit of background. A source of pride within the Advanced Design organization was the homegrown parametric sizing tool, known as WISE (Weight Integrated Sizing Evaluation). In fact, during the early ATF studies (1976-1981) one of the few attaboys that the Air Force Flight Dynamics Lab (AFFDL) engineers in Dayton often passed on to Grumman was how thorough and believable the parametric-based weight estimates appeared, as compared to the 'competition'...

The X-29 design was initially drawn in late 1977, and the configuration was sized with the following weight values:
TOGW = 16.000 lb. Fuel wt = 4,000 lb. Maneuver Design wt = 14,000 lb (50% fuel).

With the 185 sqft forward swept wing, the intended lift coefficient at the FSW design point (4.5-g sustained, Mach 0.9, 30Kft altitude) was: CL = (4.5*14,000)/(356*185) = 0.955

Fast forward to the Dec. 1984 first flight, the X-29 actual weight values were:
TOGW = 17,700 lb. Fuel wt = 3,978 lb. Maneuver wt @50% fuel = 15,710 lb.

The actual TOGW was a bit more than 10% higher than the initial parametric estimate. I'll leave it to the audience to decide how good or bad a prediction this was.

Relative to the Northrop/Grumman/Vought ATA effort, I'll add that Grumman-Bethpage sent absolutely their first-string team to Northrop-Pico Rivera (nope, I wasn't picked). One of the Grumman technical leaders told me that he was under the impression that "Northrop has the C-team on the program" -- which in hindsight makes sense: ATB/B-2 first string; ATF/F-23 second string; ATA third string.
The Grumman X-29 was a Technology demonstrator aircraft program. Development costs and schedule time for the X-29 were also minimized by reuse of existing aircraft components like the fuselage from an F-5. This made estimation of aircraft weight a much different challenge than for a clean sheet production stealth aircraft like the ATA.

Based on the three Northrop programs phase start dates and my industry experience, ATB preliminary design engineers would have been transitioned over to the ATA program. This may explain the Northrop Grumman mini me B-2 version for the ATA proposal.
 
Last edited:
The Grumman X-29 was a Technology demonstrator aircraft program. Development costs and schedule time for the X-29 were also minimized by reuse of existing aircraft components like the fuselage from an F-5. This made estimation of aircraft weight a much different challenge than for a clean sheet production stealth aircraft like the ATA.

Based on the three Northrop programs phase start dates and my industry experience, ATB preliminary design engineers would have been transitioned over to the ATA program. This may explain the Northrop Grumman mini me B-2 version for the ATA proposal.
I think we had a very good ATA design and having the "C-team" on the effort makes sense, we (N/G/LTV) just thought the fixed-price contract made no sense and had too much risk. Our "mini-me" B-2 made sense, with our experience on B-2, Tacit Blue, ATF and other programs not to mention trying to convince the USN to attack from mid to high altitudes for an LO platform, the USN was wrapped round the axle with a direct A-6 replacement and flying on the deck, I've stated this previously in other posts, an LO subsonic flying wing on the deck; no, no, no. I think we could have given the USN a very good aircraft but you have to use common sense as well. Plus, large-scale LO programs were new territory for military aviation during this period, difficult problems to solve and things had to be invented. Our full-scale ATA mock-up in the "blue and gold" room at Pico was pretty and I think our friends at Grumman built it. Very sad seeing it cut up though.
 
I think we had a very good ATA design and having the "C-team" on the effort makes sense, we (N/G/LTV) just thought the fixed-price contract made no sense and had too much risk. Our "mini-me" B-2 made sense, with our experience on B-2, Tacit Blue, ATF and other programs not to mention trying to convince the USN to attack from mid to high altitudes for an LO platform, the USN was wrapped round the axle with a direct A-6 replacement and flying on the deck, I've stated this previously in other posts, an LO subsonic flying wing on the deck; no, no, no. I think we could have given the USN a very good aircraft but you have to use common sense as well. Plus, large-scale LO programs were new territory for military aviation during this period, difficult problems to solve and things had to be invented. Our full-scale ATA mock-up in the "blue and gold" room at Pico was pretty and I think our friends at Grumman built it. Very sad seeing it cut up though.
With the ATB proposal effort being years before the ATA, my guess was that the ATA was staffed with ATB preliminary design engineers. Was this guess correct? The B-2 rolled out of it's hanger for public view in November 1988, and the ATA contract was awarded in January 1988.
 
1. The Grumman X-29 was a Technology demonstrator aircraft program. Development costs and schedule time for the X-29 were also minimized by reuse of existing aircraft components like the fuselage from an F-5. This made estimation of aircraft weight a much different challenge than for a clean sheet production stealth aircraft like the ATA.

2. Based on the three Northrop programs phase start dates and my industry experience, ATB preliminary design engineers would have been transitioned over to the ATA program. This may explain the Northrop Grumman mini me B-2 version for the ATA proposal.
1. The F-5A forward fuselage, cockpit, nose gear were reused, the rest of the X-29 airframe was all-new. Subsystems were off-the-shelf, and the main landing gear was from F-16A. Two fellas (Glenn Spacht and Nate Kirschbaum) set these groundrules and instructed the configuration designer and the 3 or 4 other project members in the Fall of 1977. These weights were readily accessible, except some subsystems were TBD. But your point is well taken, it wasn't a completely new build, and there was no intention to produce more than 2 articles.

Since the F-14A first flight in Dec. 1970 until the ATA competition began in Nov. 1984, other than the X-29, Grumman had:
  • modified an A-6 to the Circulation Control Wing demonstrator;
  • modified a batch of F-111As to the EF-111A;
  • designed mods for 707-320 airliners to the E-8A/C JSTARS;
  • modified and refurbished A-4s for Malaysia;
  • assisted Gulfstream in the design of the Gulfstream III wing;
  • designed and built the composite wing and tail for Israel's Lavi fighter;
  • did the early engineering work for the A-6F and the F-14D;
  • sustained the F-14A, A-6E, EA-6B, E-2C and C-2A.
Not many choices besides X-29 to evaluate Grumman's weight prediction proficiency relative to ATA.

2. The gentleman who made the C-team comment to me (and he was a gentleman) would not have been aware of Northrop's plans if and when the N/G/V team was awarded the EMD contract.
 
Since the A-12/ATA thread has had some traction in the last few weeks I thought I would share some pictures I took at the Fort Worth Aviation Museum in November 2025. The A-12 Avenger II mockup remains under wraps... unfortunately it appears the right wing tip had started to warp or may have been damaged at some point. I didn't realize until going back through this thread that the museum also had a mockup of the engine and exhaust so the only pictures I have of it are secondary (right next to the OV-10 Bronco in their "junk yard") or from a distance (you can see part of the wrap and exhaust in this picture I have of the F6U Pirate's tail).

I was told by one of the museum's volunteers that there are plans to get the museum's collection, including the A-12, in to indoor protection, but I don't know if there is a window for that or how definite that might be.
 

Attachments

  • PXL_20251112_180805540.jpg
    PXL_20251112_180805540.jpg
    3.2 MB · Views: 61
  • PXL_20251112_182110222.jpg
    PXL_20251112_182110222.jpg
    3.5 MB · Views: 61
  • PXL_20251112_175532940.jpg
    PXL_20251112_175532940.jpg
    4 MB · Views: 61
  • PXL_20251112_175508084.jpg
    PXL_20251112_175508084.jpg
    4.9 MB · Views: 61
  • PXL_20251112_175448074.jpg
    PXL_20251112_175448074.jpg
    4.9 MB · Views: 85
  • PXL_20251112_165544353.jpg
    PXL_20251112_165544353.jpg
    3.2 MB · Views: 96
  • PXL_20251112_165427095.jpg
    PXL_20251112_165427095.jpg
    2.9 MB · Views: 101
  • PXL_20251112_163327868.jpg
    PXL_20251112_163327868.jpg
    2.5 MB · Views: 98
  • PXL_20251112_163312953.jpg
    PXL_20251112_163312953.jpg
    2.4 MB · Views: 90
  • PXL_20251112_163300734.jpg
    PXL_20251112_163300734.jpg
    2.2 MB · Views: 113
Makes for an interesting comparison to the F-14A/original B.

Design spec empty weight was 36,000 lbs, and as delivered (early blocks with with TF30-P-412's) was ~38,200. The intended F401's (as flown in ship 7) brought that down to 37,000 lbs which gives an overage of only 3%. Not too shabby for such a complex aircraft.

Of course, by the time they got to the D, empty weight ballooned to almost 44,000 lbs (and that was with wing glove vane deletion)
...but that wasn't Grumman's fault.
 
Makes for an interesting comparison to the F-14A/original B.

Design spec empty weight was 36,000 lbs, and as delivered (early blocks with with TF30-P-412's) was ~38,200. The intended F401's (as flown in ship 7) brought that down to 37,000 lbs which gives an overage of only 3%. Not too shabby for such a complex aircraft.

Of course, by the time they got to the D, empty weight ballooned to almost 44,000 lbs (and that was with wing glove vane deletion)
...but that wasn't Grumman's fault.
So what exactly happened? Routine equipment additions should not drive up empty weight by roughly 6,000 pounds. Does this mean the airframe structure requires extensive reinforcement?
 
To support my claim that I was actually on the A-12 program, I took a photo of my program coffee cup. I gave away my A-12 badge extender a couple years ago to a FARA program manager after the US Army canceled his program. I wanted to let him know I felt for him, and that it could have been a lot worse.

I was deployed by MCAIR to the ATA proposal effort to support the canopy actuation and escape system RFP response sections. On my first ATA trip to Fort Worth to meet with our GD partner, I discovered that the older GD good old boy's on the ATA didn't like having to listen to a 'Carlos' comment on their canopy design. This led to me telling a GD Chief engineer that he didn't know squat on canopy jettison loads. I was pulled out of the meeting by the MCAIR Chief, reprimanded, being told 'I don't care that you are right, still you don't tell a GD Chief that he doesn't know squat. Even if he is being an asshole". The link below is to a video of A-12 Ingress Egress compliance testing conducted in March of 1989 at MCAIR. Sorry for the quality, but it is the best VCR tape restoration current software can generate.

Enjoy

A-12 Ingress Egress Video March 1989
Since you were part of the engineering effort for the A-12, on the McDonnell Douglas side of things, I have a question for you. By 1988 most of the basic shape of the aircraft was probably frozen. During that same year the B-2 was first revealed (the initial painting in the spring of 1988 and the rollout that November) and also the reveal of the F-117 that November. Was there ever any conversation on whether anything needed to change on the A-12 to improve its low observables? Or was it ultimately too late in development and would have added too much more to the program?
 
So what exactly happened? Routine equipment additions should not drive up empty weight by roughly 6,000 pounds. Does this mean the airframe structure requires extensive reinforcement?

The F110's added an additional 800 lbs, the D's dual TCS/IR pod probably added a couple hundred more. I wouldn't be surprised if the new electronic/radar gear added to the D (especially the A to G gear) added significant weight. Then there probably was some structural reinforcements added over the years. How much, I have no idea.
I'm guessing all those factors combined could account for the ~3500 lb weight increase from the A to the D, but the 2000 lb increase from early A to later A is a mystery to me.
 

Similar threads

Back
Top Bottom