Comments by "LRRPFco52" (@LRRPFco52) on "Sandboxx" channel.

  1. 76
  2. 35
  3. 29
  4. 23
  5. 23
  6. 17
  7. 15
  8. 14
  9. 12
  10. 12
  11. 12
  12. 11
  13. 11
  14. 10
  15. 10
  16. 10
  17. 9
  18. 8
  19. 8
  20. 8
  21. 7
  22. 7
  23. 7
  24. 7
  25. 7
  26. 7
  27. 6
  28. 6
  29. 6
  30. 6
  31. 6
  32. 6
  33. 6
  34. 6
  35. 6
  36. 5
  37. 5
  38. 5
  39. 5
  40. 5
  41. 5
  42. 5
  43. 5
  44. 5
  45. 5
  46. 5
  47. 5
  48. There are F-16XL test pilot reports openly published now. They loved the performance and handling, but all complained about the loss of T/W ratio. It had longer legs than anything except the Vark. The USAF fighter culture was heavily focused on the new capabilities of the F-15 and F-16, with pilots rating fighters by how well they could retain energy and execute excellent climb rate, as well as improved visibility from the teen series cockpits. HOTAS was also a new thing and a big deal, since many had F-4 experience to compare and contrast against. The XL was seen as a step backwards in the energy department when it came to turns, but was better at straight and level flight than the others. You didn’t need to touch burner to refuel when combat-configured like you do in a Viper.   The big pluses with the XL were combat radius and stores per sortie. You could service multiple TGT sites and TGT sets in a single sortie and still have tons of station time without need to refuel. If half of the F-16s in Desert Storm were F-16XLs, it would have increased the amount of deliverable ordnance in a much lower overall sortie count, which could have cut the length of the bombing campaign down. In combat configuration on an F-16A or F-16C, you only really have 2 primary mission-relevant weapons stations available. Every single other station is occupied with ECM, FLIR, or EFTs, plus AAMs for self-defense or rare opportunistic A2A TGTs that somehow slipped through the Grey Eagle’s claws.
    5
  49. 5
  50. 5
  51.  @Fng_1975  I’m not sure what Navy sources you’re listening to, but the major comments coming out of the current deployed carrier air wing operating F-35Cs is that they finally got long legs back to the strike group. That and the networking are the main things they’re talking about. (MEZ I’m referring to is Missile Engagement Zone common to modern IADS, not legacy IADS where Tomcats, Hornets, and A-6Es were shot down). The F-35B for the USMC and UK has the same mission radius as a 2-tank F-16C or better, and it has the least amount of internal fuel of the 3 separate airframe designs (there isn’t 1 airframe design). F-35B carries 13,500lb, about the same amount of internal fuel as an F/A-18F, but only has one engine and mostly a clean aerodynamic profile for most common configurations. The F-35A carries 18,250lb internal, while the F-35C for the Navy carries 19,200lb, while having very large wing and tailplane area. Senior F-14 pilots who worked on F-14D development praise the JSF program, as do all the pilots who convert into it. The criticism isn’t from people close to JSF, but from people who don’t know what they’re looking at and have very limited frames of reference to it. JSF is legit. I’ve called in CAS as well, so I know somewhat about that mission set and legacy profiles vs the modern profiles for weapons employment. Even the A-10C has gone to SDBs and LGBs as primary weapons, superseding the AGM-65G and CBUs from the A-10A profiles. There is no reason for the down-on-the deck close target eyeball CAS profile nowadays with SDB. The whole re-attack requirement for A-X in the early 1970s is what really pushed the A-7D out, which should not have happened. A-7D had crazy legs better than any of the teen series, including the F-15E. JSF-A and -C bring back the range/radius of the A-7D/E basically, but with better payload and the ability to do A2A better than the Raptor in many ways (IR spectrum sensor fusing with RF).
    5
  52.  @Fng_1975  You'll find National Interest isn't a reputable source for information on any of this, but one of the many ad revenue click-bait sites. With the Super Hornet, Fleet Air Defense sortie generation increased over the Tomcat and with Block II SH with the AESA Radars and JTIDS, the detection ranges and coverage smokes the APG-71 & AWG-9 easily. F-14D doesn't compare well to a Block II Super Hornet in that regard, especially with ATFLIR slaved to the AESA. Regarding CAS with JSF: F-35s can PID from over the horizon in bad weather at night better than A-10 can do in clear wx on top of you, and PID both Blue and enemy forces in ways that really push more into what was traditionally spyplane and ELINT aircraft territory. The resolution of the early Radar Ground Mapping TGT mode was good enough to count windows on buildings at 80 nautical miles, which it fuses with the zoomable EOTS FLIR in the nose. At certain very far distances, they can read your IFF patches. F-35s don't use the legacy omnidirectional data link network like previous gen fighters. They have adapted comms with it, but MADL is extreme narrow beam LPI, so it can't be intercepted between F-35s, and they can specifically direct who they're sending to in a high ECM environment. A-10s have been involved in more Blue-on-Blue dating back to ODS, killed many US, UK, and Canadian forces in ODS, OEF, and OIF, all using visual approaches even against units with VS-17s clearly visible. I've seen the HUD footage with comms traffic. They threw PID out the window with buck fever, slaughtered guys in their APCs on multiple occasions, and stray rounds on danger close runs are high probability with a pilot with less than 1000hrs of experience. That's why A-10C has been focused on using Small Diameter Bomb, GBU-12, APKIWS, and GBU-31 vs the legacy weapons assortment. If you talk with JTACS who have actually employed F-35s, the story is totally different than what "experts" have been saying about F-35 and CAS. They were shocked what the F-35 pilots could see and know around them, while not even being visible or heard from the ground. You can't deceive the MADL networked fused picture from the AESA, EOTS, DAS, and RF sensor suite. You can't get anything in between 2 F-35s linked via the MADL, so now you have triangulation of over 30 different sensors covering the entire signature spectrum, 28 of those sensors being passive. It forces CAS into a new generation of capability that's hard for legacy TACPs and JTACs to understand without a detailed capes briefing. It not only exceeds what is known or expected in a traditional 9 line approach, but opens up Electronic Warfare options that were typically provided by certain fixed wing platforms that are vulnerable to MANPADS and AAA. In many cases, JSF can provide 10 digit coordinates to your organic fires assets and help manage the fight that way without needing to drop anything, while conducting exploitation of the extended threat forces order of battle and TGT their mobile nodes, tunnels, bunkers, Radios, vehicles, and nearby supporting forces. They see and share things that make the EW, ELINT, and AWACS systems officers envious without even breaking squelch. It's a revolution in CAS as we know it. As to airframes, they're all quite different, but share sensors and much of the propulsion to reduce costs from what was being proposed. If you look back at all the designs being explored during ASTOVL, then JAST, almost everyone had settled on the same basic fuselage configuration independently, with different variations in wings, canards, and tailplanes. The McDonnell Douglas fuselage/nose designs looked the same as Lockheed. There were dozens of these designs. Merry Christmas to you too!
    5
  53. 5
  54. 5
  55. 5
  56. 4
  57. 4
  58. 4
  59. 4
  60. 4
  61. 4
  62. 4
  63. 4
  64.  @quasimotto8653  It’s physically impossible to integrate the sensors, IPP, internal weapons bays, and VLO features into any 4th Gen platform. The entire mold line and bulkheads all have to change for starters, which means a completely-new airframe design. At that point, you’re back into the design cycle that resulted in F-35. There’s no place for DAS, MADL, and EOTS on the Viper. These technologies were tested on the AFTI F-16 at Edwards, which is the coolest F-16 you will ever see. They put LANTIRN pods in the LEX roots so you wouldn’t have left or right blanking of the pilot’s FOV when trying to lase or observe a ground TGT with the FLIR. That’s more expensive than going the EOTS route, since EOTS is centerline under the nose. The Flight Control System in the F-35s are actually more simple than in the Viper since they have independent ElectroHydrostatic Actuators (EHAs), with their own self-contained hydraulic fluid that doesn’t need to be piped under pressure to them from the central hydraulic reservoir and pumps. This makes safety and maintenance so much better than the Viper, and they’re not fly-by-wire, but fly-by-light. On the Viper, if replacing an actuator assembly, you have to bleed the hydraulics, disconnect the FBW system, disconnect the hydraulic line, unbolt the fasteners, install the new unit, fasten, reconnect the FBW, reconnect the hydraulic line, re-fill the hydraulic reservoir, pressure up the system and measure if it is too full or not full enough, and you have to manually index the actuator position with the control surface to make sure they’re tracking correctly with each other and the DFLCS position cues. With the EHAs in F-35, you disconnect the fiber optic line, remove the fasteners, pull the assembly, install the replacement EHA, reconnect the fiber-optic line, the system automatically indexes the actuator to the control surface position and registers the position with the DFLCS....done. Maintainers complain that it basically maintains itself.
    4
  65. YF-23 cracked several windscreens in supersonic tests, so it never exceeded Mach 1.82 if I recall the graphs correctly. It also had problems with the intakes and boundary layer control systems at supersonic speeds. It also had dual actuators laid sideways for each control surface so they could keep the thickness of the wings as thin as possible for VLO, but added mechanical complexity to the FLCS. It still didn't have a solution for its weapons bay storage and ejection racks, and couldn't carry as many weapons as the YF-22. All of these issues represented serious cost risks to the whole program, so even though it met the requirements, it was a much riskier option from a company that had already demonstrated massive cost overruns with the B-2A in production and delivery to USAF. The YF-22 PAV-1 (GE YF-120L motors) was the only ATF prototype that exceeded Mach 2. They already had weapons bay solutions for AIM-9 & AIM-120 with demonstrated separation capability, and had an excellent bowless canopy with all-around view. The one area the YF-22 failed was weight. It was too heavy for the desired 1.2 T/W ratio on take-off, so engine performance increased to 35,000lbs per in production. As a result, the F-22A has monstrous T/W ratio and excess thrust throughout the regime. If the YF-23 had gone onto the F-23A, it was going to grow even more in length to accommodate another forward weapons bay and still not have the weapons load that the F-22A has. There were aspects of the YF-23 test pole model that had better VLO, but others on the YF-22 test pole that were better, especially looking at serpentine intake ductwork vs the YF-23's partially-exposed cold stage turbofan inlet guide vanes from lower frontal-oblique angles. Best thing going for the YF-23 was combat radius/range.
    4
  66. 4
  67. 4
  68. 4
  69. 4
  70. 4
  71. 4
  72. 4
  73. 4
  74. If you look at the average life of carrier aviation jet platforms, the F-14 series had a nice long run of 32 years, which was pretty normal compared to the F-4B/J/N, A-4, A-6, A-7A/E, and even the F/A-18A-D. All the A model airframes were trashed/timing out by the 1990s. The flight control system problems still remained in the D until it dealt with them with the DLFCS upgrade, but the mechanical architecture still had all the same issues. Wing sweep mechanism box was Titanium, and required electron beam welding. The Navy spent $369 million on development of a new engine for the F-14 in the early 1970s (1970-1973), the Pratt & Whitney F401-PW-400, which was an F100 variant to share commonality with USAF engines in the F-15 for better management from an industrial perspective. That engine never got put into the planned F-14B, and all that money was basically blown very early in the program, leaving the Tomcat with the temporary stop-gap TF30 engine from the F-111 program. The costs seem to have robbed the F-14 of additional upgrades that all the other teen fighters got. AWG-9 was a nightmare too, with disconnection issues, tubes, antiquated display for the RIO that burned images into the screen, and the system suffered from lag and drag when offsetting for better angles at BVR. F/A-18s regular out-performed F-14s even in the BVR fight, and that was before the Super Hornet. F/A-18 had a Radar that could look-down/shoot-down over land and sea, whereas AWG-9 only worked over the ocean (when it did work). There wasn’t enough processor memory to handle ocean and land background clutter when the F-14 and E-2 Hawkeye were developed. That changed in the mid-late 1970s with the solid state electronics and digital revolution, which hit at just the right time for the F-15, F-16, and F/A-18. F-14 just barely missed the boat on that one, and had its whole combat avionics architecture built on the AWG-9.
    4
  75. 4
  76. 4
  77. 4
  78.  @markwalker3499  JSF production is over 716 airframes, which is more than Rafale, Typhoon, or Super Hornet and built in less time than any of those fleets. Will not be “a couple of trillion soon” since we haven’t even reached the initial acquisition costs of $251 Billion for 2,456 JSF-A/B/C for the 3 services. The worst-case forecasts from bean-counters in the Pentagon is $1.5 trillion by the year 2070 for all 3 variants, upgrades, and operations and maintenance costs over the life of the program. That averages $25 Billion per year from a $767 Billion defense budget, with that $25 Billion divided by 3 services, most of which will be USAF. 6th Gen is meant to integrate with JSF, using JSF data link architecture. They are also meant to replace top-end fighters in USAF and USN like the F-22A and Super Hornet, not in the same track for JSF series. JSF is superseding F-16C, F-117A, F/A-18A-D, AV-8B, EA-6B. There are always multiple fighter tracks in each service. I know you don’t realize this, but F-15EXs cost more than F-35As by quite a bit, and cost more to operate. F-15EX at a minus with its relevant combat systems attached so it can reach a fraction of F-35 performance take it up to over $103 million per airframe/pods/EPAWSS minimum. The baseline stripped aircraft with no pylons, fuel tanks, FLIR sensors, EW system, or the new Legion IRST pod costs $87.7 million. When you add the CFTs, 12 specific pylons that attach to the CFTs, wing and centerline pylons, LAU rails, and ejector racks, the price goes up even more over $103 million. That’s a non-deployable F-15 into the high-threat areas of the world, unless F-35s fly ahead of it and provide EW support. Wherever you got the idea that 10 or 12 F-15s cost what one F-35 does, the math is way off and flipped. You can buy 1 F-35A with its full weapons suite, spare parts, support, and still be less than an F-15EX with no weapons at all.
    3
  79. 3
  80. 3
  81. 3
  82. 3
  83. 3
  84. 3
  85. 3
  86. 3
  87. 3
  88. 3
  89. 3
  90. 3
  91. 3
  92. 3
  93. 3
  94. 3
  95. 3
  96. 3
  97. 3
  98. 2
  99. 2
  100. 2
  101. 2
  102. 2
  103. 2
  104. 2
  105. 2
  106. 2
  107. 2
  108. The A-10 was conceived and built as an armed escort for Airmobile units because of Vietnam, which I’ve been forced to consider was an ill-advised concept outside of SEA. They had A-1 Skyraiders that were perfectly capable of armed escort for rotary wing formations, but the A-1 didn’t have the payload to take out the emerging self-propelled AAA platforms like the ZSU-23-4 and tanks. The A-7D had that capability, but couldn’t re-attack with visual acquisition on its first pass like the A-1 could. So they basically wanted select features from the A-1 and A-7 combined into one, purposely handicapping its power so that it would be slow, while giving it more payload to be able to bust tanks with AGM-65s, drop CBUs on light vehicles and troops in the open, 500lb bombs on emplaced gun positions and relay stations and trucks, then use the 30mm gun once other ordnance was expended. The A-10 was especially ill-suited for the European Theater of Operations with NATO, since it was a suicide mission into Soviet mobile IADS nets that were part of their armored regiments, made even more unsurvivable with the advent of SA-6 and double-digit SAMs. The A-7D was a much better for for the Fulda Gap. In ODS, the A-10 had to be grounded until strike aircraft could effect the D-SEAD mission set and clear out most of the AAA and SAMs, because they shot down or damaged so many A-10s in the first 2 weeks of the war. 20 of them were lost (7) or damaged (13) from Iraqi AAA and SAM fire from January 17 - February 27, 1991. It was still very effective once SEAD had been conducted, but the F-111F as just one example, killed more tanks than all A-10s combined in 1/4 the sorties flown by A-10s. F-111F with PAVE TACK Pod and LGBs was a brutal hunter of Iraqi tanks at night. Only 3 F-111Fs were hit by AAA, able to return safely to base each time, no losses. It was one of the most survivable platforms of the war.
    2
  109. 2
  110. 2
  111. 2
  112. 2
  113. 2
  114. 2
  115. 2
  116. 2
  117. 2
  118. 2
  119. 2
  120. 2
  121. 2
  122. 2
  123. 2
  124. 2
  125. 2
  126. 2
  127. 2
  128. 2
  129. 2
  130. 2
  131. 2
  132. 2
  133. 2
  134. 2
  135. 2
  136. 2
  137. 2
  138. 2
  139. 2
  140. 2
  141. 2
  142. 2
  143. 2
  144. 2
  145. 1
  146. 1
  147. 1
  148. 1
  149. 1
  150. 1
  151. 1
  152. 1
  153. 1
  154. 1
  155. 1
  156. 1
  157. 1
  158. 1
  159. 1
  160. 1
  161. 1
  162. 1
  163. 1
  164. 1
  165. 1
  166. 1
  167. 1
  168. 1
  169. 1
  170. 1
  171. 1
  172. 1
  173. 1
  174. 1
  175. 1
  176. 1
  177. 1
  178. 1
  179. 1
  180. 1
  181. 1
  182. 1
  183. 1
  184. 1
  185. 1
  186. 1
  187. 1
  188. 1
  189. 1
  190. 1
  191. 1
  192. 1
  193. 1
  194.  @ericpotter4657  The Navy was faced with several different paths moving forward after the failure of the A-12 program (almost $2 billion thrown down the drain with that). The A-6E had already proven to not be survivable in ODS and airframes were timing out anyway, so A-6E would be last of the subsonic medium attack capability in the Carrier Air Wing. That created a big void in strike capability looking at payload and range, plus the various mission sets A-6Es could perform including SEAD with the HARM. The more expanded multirole versions of the F-14 like ASF-14 and ST-21 were one path to consider. Pros were the possibilities in payload, range, improved avionics, and multi-mission set wing-role options with more clean sheet structural/propulsion/electronics evolutions of the Tomcat. Cons were 1) risks associated with an airframe design whose complexity never allowed it to realize a consistent mission readiness rate much above 60% throughout its career, 2) Costs spiraling away from any initial projections, which were already high, 3) Continual discoveries of systemic problems with F-14 structures even into the late 1990s/early 2000s, 4) The discovery that the AIM-120 required a new solution to the wing glove pylons due to aerodynamic problems with separation and roll, 5) Requirement for a 2 crew platform demand on the training pipeline, and 6) the incompatibility with the design yielding to application of Low Observables. Another option for NAVAIR was to adopt an enlarged Hornet with bigger motors, taking advantage of the development of the A-12 engines and making them afterburning, increasing the combat radius to match the F-14’s, adding 2 more weapons stations for a total of 13, acquiring a force mix of mostly single seat E models, but with enough 2-seat F models to handle the A-FAC mission and some other more involved strike and SEAD mission sets where a WSO would be helpful, and incorporating some low observables into the airframe design, specifically with the intakes and serpentine airflow geometry to hide the inlet guide vanes and fans from line of sight RF reflectivity. While the maintainability of the Baby Hornet fleet was overstated initially, it was still quite superior to the Tomcat, which helped increase readiness rates of the air wing while afloat, with far less MMHPFH exerted by Hornet wrenchers. It also had a more reliable avionics suite that used solid state/digital revolution along with the moving map display, and could genuinely flip from A2G to A2A while headed to prosecute strike missions, and had Non Cooperative Target Recognition capability that the F-14 didn’t have. Especially after Desert Storm, the tables flipped from all the ridicule that Hornets had received from the Tomcat community for "not being real fighter pilots", etc., to Tomcat guys eating crow for not getting any fighter kills in the most target rick environment since Vietnam (far more fighters than Vietnam has or ever will have). From the big picture, NAVAIR looked at these 2 paths and saw a lot of risks and challenges with the ASF-14/ST-21/Super Dooper Tomcat, vs less risk with the Super Hornet, and went with the Super Hornet. The acquisition costs alone for any Super Duper Cat were a known larger quantity than Super Hornet for sure, as was the training pipeline for an all 2-man crew platform. In secret, the US Navy had already been working with Royal Navy, USAF, DARPA, and USMC on a next generation stealth platform anyway, which would benefit from all the RDT&E spent on A-12 and ATF, so AST-14/ST-21 might have threatened that program as well. Imagine trying to acquire JSF-C right now while also supporting a Super Duper Tomcat fleet. The Navy is going to be talking more about how they wish they had more F-35Cs than Super Hornets after this current deployment, and they already announced a 20% reduction in upgrades from Block II Super Hornets into Block IIIs.
    1
  195. 1
  196. 1
  197. 1
  198. 1
  199. 1
  200. 1
  201. 1
  202. 1
  203. 1
  204.  @WembysTRexArms  There is a 360° passive RF sensor network fused with the 360° IR DAS, so it does have a level of surround situational awareness that doesn't exist on other fighters. The RAM is not compromised from flying within its performance regime, including supersonic. There were 2 of the 6 original developmental F-35s, 1 F-35B and 1 F-35C that exhibited some slightly higher temps in the h-stabs that concerned engineers because of embedded antennae in those structures. They tried duplicating the problem on the other birds with extended supersonic runs, dives, and maximum Mach value between 2 tankers up and down the East coast, and never saw those temps in those structures again. The production F-35s after that didn't even use the same materials in the rear tailplanes, so the whole thing was a fluke. That was over 10 years ago, never duplicated. The F-35 series doesn't rely on RAM paint like other VLO designs. The paint is mostly IR spectrum camouflage. The physical structure of the 3-later skin has carbon nanotubes with wide spectrum RF energy defeating characteristics. The common maintenance access points have seam covers that don't require removal of and reapplication of RAM paint or treatments. There are periodic inspection and mx points like around the wingtip nav lights that have RAM tape covering them that does need to be scraped and reapplied, but they aren't day-to-day squadron-level operations. As a result, F-35A has less than half the mx hours of a stripped, new F-16. It's just a vastly-superior aircraft from a mx perspective, and former F-16 wrenchers have said as much repeatedly.
    1
  205. 1
  206. 1
  207. 1
  208. 1
  209. 1
  210. 1
  211. 1
  212. Anyone who refers to the Century Series as a model to emulate now, clearly has no freaking clue what the Century Series was. Each design never really reached its intended potential, and several of them served their ultimate purpose as QF-1xx target drones for AIM-120s. F-101A was meant to be a Strategic Air Command supersonic escort fighter. Due to transcontinental capability of bombers, that was ill-conceived, so they made the F-101B interceptor variant, and RF-101B tactical recon variant. F-102 was meant to be a higher supersonic interceptor. Couldn't reach much more than Mach 1.2 clean, was put into Air National Guard service quickly. F-104 was never asked for by USAF, and instead served as an interceptor or multirole fighter among NATO partners. USAF literally had no use for it outside of flight sciences and NASA test bed work at Edwards AFB. F-105 was meant to be a supersonic tactical nuclear strike fighter. Early variants were structurally unsound, broke apart in-air, so it had to be upgraded and was most produced in the F-105D model. This was probably the most successful of the century series, but it had all sorts of problems, was shot down in Vietnam repeatedly, until being replaced largely by the F-4 and F-111. F-106 was what the F-102 was meant to be, but was limited to Air Defense Command as a Mach 2 interceptor. This video incorrectly showed a Mirage in place of the F-106. The real success story of that era around the Century Series was the F-4 Phantom II, which wasn't a Century series at all, but initially a US Navy fleet defense interceptor.
    1
  213. 1
  214. 1
  215. 1
  216. 1
  217.  @xyzaero  Demonstrating carriage and separation does not equal multirole. You have to work out the systems, implement the profiles into weapons manuals, and train on those in order to be truly multirole. Grey Eagles and F-14A never had that. F-14A didn't even have the AIM-54A working throughout the 1970s, and was hit & miss in the early-to-mid 1980s until the bugs were ironed out and the -54C finally got into the fleet. There's only so much money for things. With F-14A, they burned $369m on the F401 engines in the 1970s, which were never produced. That was supposed to be the production motor for the F-14B, with only a handful of initial F-14A LRIP birds as stop gaps. After that fiasco, Tomcat money was allocated to developing the TF30-P-412A into the P-414A. They were hurting on RWR and other systems money and didn't get ALR-67 until much later, and were stuck with an old analog AWG-9 Radar that couldn't look-down/shoot-down over land. Same with AIM-7F integration from AIM-7E2, then AIM-7M and AIM-9L. These aren't plug-and-play, but require a lot of testing and systems integration, live fire weapons testing on TGT drones, and weapons manual additions, as well as weapons school syllabus updates. With F-15, the money went for Radar upgrades when we did Programmable Digital Signals Processor that went into F-15C, plus its EW systems were sucking up funds to get that side working better. We also had problems with the F100-PW-100 motors. Nozzle sections ripped off at high supersonic speeds, and it suffered compressor stalls, AB unstarts, and blades letting go. All the money going into F-14A and F-15A-D upgrades was focused on propulsion, A2A Radar, A2A weapons, and EW equipment. None of it was going towards A2G. The only funded additional role for Tomcats was for select F-14As to become TARPS birds as we retired the RA-5C Vigilante. The multirole F-15E was and is treated as a separate program, though we did have both F-15C/Ds and F-15Es on the CTF at Edwards. There was cross-pollination in A2A modes between APG-63, APG-70, and APG-71, but Grey Eagles never got any of the A2G capes from the APG-70 because it wasn't part of Grey Eagle community mission set allocation or training.
    1