Tuesday, July 7, 2026

Willie the Whale: How the F3D Skyknight Took Back the Night Sky Over Korea

MiG-15s Owned Korea's Night Skies — Until America Sent In One Radar Jet That Never Lost

A Naval Institute Proceedings–style feature

BLUF (Bottom Line Up Front)

By late 1951, Soviet-flown MiG-15s — cued by ground radar and searchlight belts — had made night bombing over North Korea nearly as costly as daylight raids, and the U.S. Air Force's stopgap night fighters (F-82, F7F, F-94) could not fix the problem. The answer came not from the Air Force but from a Marine Corps squadron flying a subsonic, straight-winged, carrier-derived jet the fighter community openly mocked: the Douglas F3D-2 Skyknight, nicknamed "Willie the Whale." 

Built around a triple-radar suite (search, lock-on/track, and tail warning) and a two-man crew, the Skyknight scored the first-ever jet-versus-jet night radar kill on 2–3 November 1952 (Maj. William T. Stratton Jr. and MSgt Hans C. Hoglind), followed by the type's first confirmed MiG-15 kill on 8 November 1952 (Capt. Oliver R. Davis and WO D.F. "Ding" Fessler), and the first-ever kill by radar lock-on with no visual contact at all on 10 December 1952 (1st Lt. Joseph Corvi and Sgt. Dan George, against a Po-2 biplane). Flown by Marine Night Fighter Squadron 513, the "Flying Nightmares," the Skyknight finished the war credited with six confirmed kills (one Po-2, one Yak-15, four MiG-15s) against a single air-to-air loss, and no B-29 escorted by an F3D was ever lost to enemy action. 

Built by Douglas around a Westinghouse fire-control radar, the type went on to a second combat career as an electronic-warfare aircraft over Vietnam before handing its mission to the EA-6A, EA-6B, and today's EA-18G Growler. The lesson the Whale proved — that sensor fusion and crew teamwork beat raw speed in a contested, low-visibility environment — remains the founding logic of modern night and all-weather air combat.

The Problem MiG Alley Created

When Boeing B-29 Superfortresses first went to war over North Korea in mid-1950, they bombed by day in tight defensive formations, much as they had over Japan five years earlier, and North Korea's small propeller force could do little to stop them. That changed in November 1950, when Soviet-flown MiG-15s — products of a design effort that had studied the B-29 in exacting detail after several forced landings in Soviet territory during World War II — began operating from bases across the Yalu River in Manchuria, sanctuaried from American attack. The Navy had recognized as early as 1945 that jet-powered threats would outrun conventional piston-engine night fighters and interceptor radar of the day, which is precisely why it had already put out a demanding requirement for a radar-equipped jet night fighter before the Korean War even began.[1]

The daylight crisis crested on 23 October 1951 — "Black Tuesday" — when MiG-15s tore into a B-29 raid against Namsi airfield, and the campaign moved to night operations to escape the MiG's reach. For a season the switch worked: the B-29's own bombing radar let it strike blind, and the MiG-15 carried no radar of its own, leaving Soviet-trained night specialists (most notably Soviet ace Anatoly Karelin) dependent on ground-directed searchlight cones to expose bombers to visual attack. When that system matured in mid-1952, night losses climbed again, and the Air Force found itself with no reliable answer: the F-82 Twin Mustang and F7F Tigercat were propeller leftovers with no hope against a jet, and the classified, high-performance Lockheed F-94 Starfire was for much of the war barred from flying over enemy territory for fear its advanced radar and fire-control gear would be captured intact.

An Unwanted Airplane Solves an Unsolved Problem

The aircraft that broke the deadlock had been designed for an entirely different service and an entirely different mission. The Douglas F3D Skyknight originated in a 1945 Navy requirement for a jet night fighter carrying airborne intercept radar capable of detecting enemy aircraft at extreme range for the era — a demand so severe that Douglas's design team, led by Ed Heinemann, effectively built the radar package first and the airframe around it.[1] The nose had to be wide enough for the dish, so the fuselage grew barrel-shaped; the second crewman sat beside the pilot, not behind him, to work the scope; and the wings stayed straight and unswept. The result carried a search radar that could pick up bomber-sized targets at roughly 20 miles and fighter-sized targets at about 15, a tracking/lock-on radar that could take over at around 4,000 yards and guide the pilot to a firing position, and a tail-warning radar covering several miles to the rear to warn the crew of an attacker closing from behind.[2] Even Heinemann considered the specification nearly impossible to reconcile with acceptable speed.

Marine Night Fighter Squadron 513, the "Flying Nightmares," traded its worn-out F7F Tigercats for F3D-2s in the summer of 1952 after 1st Marine Aircraft Wing was asked to assign a night fighter squadron to escort the B-29s suffering losses on nighttime raids, flying from Kunsan (K-8) and later Pyeongtaek (K-6).[3]

The Radar: Designer, Manufacturer, and How It Worked

The Skyknight was designed and manufactured by the Douglas Aircraft Company at its El Segundo, California plant, with an initial development contract issued on 3 April 1946, under a design team led by Ed Heinemann — already famous for the SBD Dauntless dive bomber and later responsible for the A-4 Skyhawk and F4D Skyray.[4] But the airframe itself was, in an important sense, secondary: the earliest prototype had carried a leftover World War II-vintage SCR-720 radar before Douglas swapped in the new Westinghouse AN/APQ-35 on the third prototype, a change that gave the aircraft a much longer effective detection range and the first lock-on capability fitted to any airborne radar, letting the system track a contact continuously and automatically rather than requiring the operator to keep re-acquiring it by hand.[5]

The fire-control radar itself was built by the Westinghouse Electric Corporation, not Douglas — a common division of labor in the era, in which the airframe manufacturer built the aircraft around a sensor package supplied by a separate defense electronics house. The AN/APQ-35 was, in fact, three distinct radar sets integrated into a single fire-control system:

  • AN/APS-21 — nose-mounted search radar, detecting a fighter-sized target out to roughly 20 miles
  • AN/APG-26 — gun-aiming and tracking radar, achieving a weapons lock at roughly 2 to 2.25 miles and feeding continuous range and angle data for the pilot's cannon solution
  • AN/APS-28 — tail-warning radar, covering the aircraft's six o'clock out to somewhere between 4 and 10 miles depending on the source consulted

All of it was vacuum-tube technology, built before the advent of semiconductor electronics, and its sheer complexity demanded intensive, specialist maintenance to keep operational.[6][7] Period photographs of VMF(N)-513 ground crews at Kunsan show technicians with the APQ-35's radar chassis pulled and laid open on maintenance stands beside the aircraft — work that had to be repeated constantly to keep the sets combat-ready.[8]

The improved F3D-2 retained this three-radar concept but fielded it as the upgraded Westinghouse AN/APQ-36 fire-control system, which at the time of its introduction was the largest airborne fire-control radar in service. It later also equipped the Vought F7U Cutlass, and its design lineage fed forward into the AN/APQ-41 and eventually the AN/APQ-120 family that armed the McDonnell Douglas F-4E Phantom II — a direct technical throughline from the Skyknight's night-fighting radar to the fire-control systems of the supersonic era.[9][10]

Marine crews also discovered a harder edge to fighting with early radar in a contested environment: North Korean ground stations broadcast active jamming against the F3D's radar from the very start of Skyknight combat operations, degrading the crews' ability to close, positively identify, and lock onto suspected contacts — an early, and largely forgotten, taste of the electronic-warfare contest that would come to define the aircraft's second career.[6]

Firsts, in Order

2–3 November 1952 — first jet-vs-jet night radar kill. Maj. William T. Stratton Jr. and his radar operator, MSgt Hans C. Hoglind, shot down what Stratton believed was a Yakovlev Yak-15, marking the first successful night radar interception of one jet by another — though, as later research has noted, no Yak-15s were in fact reported operating in Korea, leaving the precise identity of that first target an open question even as the tactical fact of the kill itself is not disputed.[6]

8 November 1952 — first confirmed MiG-15 kill by a Skyknight. Capt. O.R. Davis and his radar operator, Warrant Officer D.F. "Ding" Fessler, downed a MiG-15 northwest of Pyongyang — a victory a ground radar intercept site had helped set up by radioing the contact's range and altitude before the Skyknight crew closed and finished the intercept on their own radar.[11] Davis would later be selected, fittingly, to fly the Skyknight's last official Marine Corps mission in 1970.[11]

10 December 1952 — first kill by radar lock-on with no visual contact whatsoever. 1st Lt. Joseph Corvi and Sgt. Dan George shot down a slow Polikarpov Po-2 biplane using radar lock-on alone, without ever seeing the target — a feat that pointed directly at the future of beyond-visual-range air combat.[6]

January 1953 — the escort force doubles. With the Skyknight's value proven, the Marine Corps doubled the number of F3Ds in Korea to 24 that month, allowing effective nightly B-29 escort, and on 12 January 1953 an escorting F3D-2 downed the type's fourth confirmed kill.[6]

The Ledger, Honestly Kept

The Skyknight was not invincible, and a fair accounting says so plainly. The type suffered a single air-to-air loss in the war, on the night of 29 May 1953, to a Chinese-flown MiG-15; separately, a Navy VC-4 detachment F3D-2 flown by LTJG Bob Bick and Chief Petty Officer Linton Smith was lost to enemy fire on 2 July 1953 while operating with VMF(N)-513 from K-6.[6] Set against those losses, F3D-2s were credited across the war with six confirmed kills — one Po-2, one Yak-15, and four MiG-15s — giving the type an overall edge of roughly eight-to-none once probable kills are counted, and no Air Force B-29 was ever lost on a mission the Skyknight was escorting.[12][6] Naval History magazine likewise records that no B-29 was lost while under Skyknight escort, even though Soviet and Chinese night fighters continued to fly over Korea throughout the period.[13] The Skyknight is credited with downing more enemy aircraft over Korea than any other single type of U.S. naval aircraft[6] — a distinction earned by an airframe fighter pilots had nicknamed for its bulk rather than its grace.

Why It Mattered, Then and Since

The tactical logic the Skyknight proved was simple and durable: in an environment where the human eye cannot see the enemy, the side with a working sensor and a crew trained to interpret it wins, regardless of which airframe is faster or more maneuverable. That is precisely the problem the Navy had anticipated as early as 1945 when it asked for a radar-equipped night jet in the first place, and Korea supplied the combat proof.[1]

That same principle — detect first, decide first, engage first — now underwrites the doctrine behind every modern sensor-fused fighter that patrols the still-divided Korean peninsula, from allied fifth-generation aircraft down to the layered ground-based radar and air-defense networks that succeeded the searchlight belts of 1952.

What the Delay Cost

None of the above should read as a tidy lessons-learned arc. The gap between the MiG-15 taking the night sky in mid-1952 and the Air Force finally turning to a Marine squadron in November was not an abstraction; it was measured in specific bomber crews.

Between November 1950 and November 1951, enemy action cost the Air Force 16 B-29s, a toll heavy enough on its own to force the daylight campaign underground.[19] The move to night bombing bought a season of relief before the Soviet searchlight-and-MiG system matured — and when it did, the cost came due in single, brutal nights rather than a gradual drift. On 10 June 1952, four B-29s of the 19th Bomb Group were caught and held by 24 searchlights simultaneously; the waiting MiGs shot down two of the four and badly damaged a third.[20] Losses like that are why the Air Force suspended night raids afterward to figure out what had just happened to it — and why, when the answer finally arrived nearly five months later, it arrived not from an Air Force program but from a Marine night fighter squadron the bomber command had to ask for directly.

The men lost or captured in that interval were not spared by hindsight. Crews shot down over the Yalu corridor in the early daylight fighting were taken prisoner and held for years; one B-29 gunner featured in a recent oral history of the campaign spent 36 months in a North Korean POW camp after his aircraft went down.[21] Another crewman shot down in January 1953 — after the Skyknight was already flying escort, but on a raid it did not cover — watched his aircraft commander stay at the controls too long to let the rest of the crew bail out, and was posthumously awarded the Silver Star for it; the gunner who survived spent the next several months in solitary confinement before reaching a POW camp.[22] By the accounting in one recent history of the B-29 gunners, the Air Force ultimately claimed 25 MiG-15s destroyed against 16 bombers lost to enemy jets across the whole war — a respectable exchange ratio in the aggregate, but one that says nothing about the men who went down in the specific window when a solution already existed in the same theater, under a different service's markings, and had not yet been asked for.[21]

That is the least comfortable reading of the interservice-lag story, and probably the correct one: the delay was not primarily a matter of unsolved technology. The airframe, the radar, and the crews were already in Korea. What was missing was the institutional habit of looking sideways at a sister service's inventory before exhausting one's own — and building that habit, rather than simply funding better hardware, is the harder problem the U.S. military spent the next three decades genuinely trying to fix, culminating in the joint-command reforms of the Goldwater-Nichols Act of 1986.

A Second War: The Skyknight Over Vietnam

The airframe's spacious, radar-friendly fuselage — the very feature that had made it a mediocre dogfighter over Korea — made it easy to repurpose as North Vietnam's integrated air-defense system began to mature. Redesignated EF-10B under the 1962 tri-service naming system, the type flew with Marine Composite Reconnaissance Squadron 1 (VMCJ-1), and on 29 April 1965 an EF-10B crew made history again, flying the first U.S. Marine Corps airborne radar-jamming mission of the war in support of a U.S. Air Force strike package. On 27 July 1965, four EF-10Bs supported a large strike against surface-to-air missile sites near Hanoi.[6] These were part of a recurring mission set nicknamed "Fogbound," in which the Skyknight jammed the guidance and tracking radars of the Soviet-supplied SA-2 Guideline missile and dropped chaff to screen strike aircraft.

The mission was not without cost. The first EF-10B lost in Vietnam went down to an SA-2 on 18 March 1966, and the type went on to lose five aircraft and twelve crewmen in Vietnam to hostile fire, accidents, and unknown causes before it was finally withdrawn from South Vietnam in October 1969 and formally retired from Marine Corps service on 31 May 1970.[6][14] Fittingly, Oliver Davis — the pilot of the Skyknight's first confirmed MiG-15 kill in Korea — was selected to fly that last official mission. By the time of its Vietnam service the type was flying more than 9,000 combat sorties,[14] an extraordinary run for a design already fifteen years old and never intended to serve past the mid-1950s. It remains, per multiple aviation-history sources, the only U.S. jet fighter type from the Korean War to also see combat in Vietnam.

Successor Technologies

The Skyknight's replacement was already in the pipeline before it left Vietnam. In the early 1960s the Marine Corps worked with Grumman to convert the two-seat A-6 Intruder attack aircraft into a dedicated electronic-warfare variant, the EA-6A "Electric Intruder," which first flew in 1963 and entered Marine squadron service in December 1965.[15][16] The EA-6A carried an AN/ALQ-86 electronic countermeasures suite and an AN/APQ-129 fire-control radar, with additional jamming equipment housed in a distinctive fin-cap fairing nicknamed the "football" and in externally carried ALQ-76 jamming pods.[17] Twenty-seven EA-6As, split between new-build airframes and A-6 conversions, fully replaced the EF-10B across the Marine composite squadrons by the end of 1969.[16]

The EA-6A itself proved an interim solution. Grumman had begun developing a far more capable four-seat derivative, the EA-6B Prowler, alongside a new integrated Tactical Jamming System; the type first flew in 1968 and entered fleet squadron service with Navy squadron VAQ-132 in July 1971, deploying to combat over North Vietnam within the year.[18] The Marine Corps took delivery of its first EA-6Bs in 1977,[16] and the Prowler went on to become, in the Navy's own description, the foremost electronic-attack platform in the U.S. military, flying missions over Grenada, Lebanon, Libya, Iraq, Bosnia, and Afghanistan.[18]

The last Marine squadron, VMAQ-2 "the Death Jesters," retired the Prowler in March 2019 after more than four decades of continuous fleet service — closing out a single unbroken lineage of dedicated Marine airborne electronic attack that ran directly from the F3D/EF-10B Skyknight through the EA-6A to the EA-6B. That retirement, without a like-for-like Marine Corps replacement, left the Corps reliant on Navy EA-18G Growler squadrons for dedicated airborne electronic attack and pushed Marine doctrine toward a more distributed model — unmanned platforms, ground-based jammers, and electronic-warfare suites embedded in the F-35B — rather than a single specialized aircraft.[14] It is the one real break in a line of descent the Skyknight started over Korea nearly seven decades earlier.

A Note on Sourcing and Discrepancies

Firsthand personnel names, dates, and unit designations above are corroborated across multiple independent secondary sources, including the U.S. Naval Institute's own Naval History magazine, the Naval History and Heritage Command, the Smithsonian's Air & Space, and standard aviation-history references. Two points of honest ambiguity are worth flagging for the record rather than smoothing over:

  • Date of the first kill. Some sources render the Stratton/Hoglind engagement as occurring "the night of 2 November 1952," others specify "the early morning of 3 November 1952" — consistent with a sortie that launched on the evening of the 2nd and scored after midnight local time.
  • Identity of the first target. The Stratton/Hoglind kill was logged at the time as a Yak-15, but postwar research has not identified any Yak-15 losses in the Korean theater, so its true identity remains unresolved in the open literature. This does not affect the tactical significance of the engagement as the first jet-on-jet night radar kill.

Sources Cited

  1. Hush-Kit, Louis Gundlach, "The Dark History of the Douglas F3D Skyknight 'Night Killer,'" 21 March 2025. https://hushkit.net/2020/12/29/enter-the-skyknight-hornet-pilot-shares-the-dark-history-of-the-douglas-f3d-night-killer/
  2. Flying Leathernecks Aviation Museum, "F3D-2 Skyknight," aircraft collection notes. https://www.flyingleathernecks.org/aircraft-collection/f3d-2-skyknight
  3. Wikipedia, "VMFAT-502" (lineage of VMF(N)-513, the "Flying Nightmares"). https://en.wikipedia.org/wiki/VMFAT-502
  4. SilverHawkAuthor, "Warplanes of the USA: Douglas F3D Skyknight, US Navy." https://silverhawkauthor.com/aviation/warplanes-of-the-usa-douglas-f3d-skyknight/
  5. Plane-Encyclopedia, "Douglas F3D, F-10 Skyknight." https://plane-encyclopedia.com/cold-war/douglas-f3d-skyknight/
  6. Wikipedia, "Douglas F3D Skyknight." https://en.wikipedia.org/wiki/Douglas_F3D_Skyknight
  7. Grokipedia, "Douglas F3D Skyknight" (tertiary reference; used only for detail consistent with sources above). https://grokipedia.com/page/Douglas_F3D_Skyknight
  8. Warbirds Resource Group, "Douglas F3D Skyknight" (design history, with period USMC ground-crew maintenance photography). https://www.warbirdsresourcegroup.org/NARG/skyknight-design.html
  9. Alchetron, "Douglas F3D Skyknight" (tertiary aggregator; cross-checked against Wikipedia). https://alchetron.com/Douglas-F3D-Skyknight
  10. Wikipedia, "AN/APQ-120 radar family" (Westinghouse fire-control radar lineage from the AN/APQ-35/36 through the AN/APQ-41 to the F-4E's AN/APQ-120). https://en.wikipedia.org/wiki/AN/APQ-120_radar_family
  11. Smithsonian Magazine (Air & Space), "The Deadliest Night Fighter in Korea," 13 May 2014. https://www.smithsonianmag.com/air-space-magazine/deadliest-night-fighter-korea-180951418/
  12. WarHistory.org, "Skyknight." https://warhistory.org/article/skyknight
  13. U.S. Naval Institute, Naval History Magazine, "The Nocturnal Professionals," Vol. 18, No. 6 (December 2004). https://www.usni.org/magazines/naval-history-magazine/2004/december/nocturnal-professionals
  14. Grokipedia, "VMAQ-2" (tertiary reference; Vietnam-era sortie and loss figures not independently corroborated elsewhere in open literature). https://grokipedia.com/page/VMAQ-2
  15. Wikipedia, "Grumman EA-6B Prowler." https://en.wikipedia.org/wiki/Grumman_EA-6B_Prowler
  16. Journal of Electromagnetic Dominance, Rick Morgan, "Semper Prowler," April 2019 (VMAQ-2/EA-6A/EA-6B lineage). https://www.jedonline.com/2020/06/20/semper-prowler/
  17. Global Aviation Resource, "Military Aviation – The EA-6B Prowler Prowls No More," 3 April 2019 (EA-6A AN/APQ-129 radar and ALQ jamming pod detail). https://www.globalaviationresource.com/v2/2019/04/03/military-aviation-the-ea-6b-prowler-prowls-no-more/
  18. Naval History and Heritage Command, "EA-6B Prowler," National Naval Aviation Museum collection notes. https://www.history.navy.mil/content/history/museums/nnam/explore/collections/aircraft/e/ea-6b-prowler0.html
  19. GlobalSecurity.org, "B-29 Operations - Korea" (16 B-29s lost to enemy action, November 1950–November 1951). https://www.globalsecurity.org/wmd/systems/b-29-ops-korea.htm
  20. b-29s-over-korea.com, "Performance of the MiG-15 in Aerial Combat" (10 June 1952 searchlight engagement, 19th Bomb Group). https://www.b-29s-over-korea.com/MIG-15/Perf_Mig-15_Combat_3.html
  21. Marine Corps Times, "'Gunners!' Revives Forgotten Chapter of Air War Over Korea," 11 November 2025 (citing James Blackwell, Gunners! B-29 Machine Gunners in the Korean War: the Aaronson POW account and the war-long 25-kills-to-16-losses tally). https://www.marinecorpstimes.com/veterans/military-history/2025/11/11/gunners-revives-forgotten-chapter-of-air-war-over-korea/
  22. HistoryNet, "Korean War: The Boeing B-29 Superfortress Served Throughout the Air War" (10 January 1953 loss and POW account). https://historynet.com/korean-war-the-boeing-b-29-superfortress-served-throughout-the-air-war/

Additional Sources Consulted (General Background)

Prepared as a factually verified, independently sourced companion piece; it does not reproduce any single source's text and paraphrases throughout, citing only for attribution of specific facts.

 

at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Willie the Whale: How the F3D Skyknight Took Back the Night Sky Over Korea

MiG-15s Owned Korea's Night Skies — Until America Sent In One Radar Jet That Never Lost A Naval Institute Proceedings–style feature ...