Background
As usual, I did a fair amount of research on Espiritu Santo and its wrecks before I ever left home on my trip, and that’s how I first came across the Corsair sitting off Turtle Bay. What caught my attention wasn’t just that it was a Corsair — one of WWII’s most iconic aircraft, with a rich history of its own. It was that, as far as I could tell, nobody had properly identified this particular wreck. That’s the kind of thing I can’t resist.
I’m also currently working on a book on aviation wrecks in Southern California. Over the years I’ve helped find and identify a number of aircraft and I enjoy chasing down unidentified wrecks. This one wasn’t connected to the book, and nobody was waiting on an answer, but the itch to try was there anyway. I also hadn’t seen evidence that anyone had built a photogrammetry model of this wreck before. This wreck needed to be dived!
The catch was that it wasn’t a given I’d actually get to dive it. I’d reached out to Jack, who owns Pacific Dive, ahead of the trip to ask about the possibility, and Joel, the dive shop manager, was upfront that it wasn’t a site they visited often — it would take some scheduling to make work. As it turned out, another diver happened to be staying up in that area of the island during my trip, which made it practical to combine the trip out with some of their other diving. Sometimes it really is just a matter of things lining up.
The Wreck
Turtle Bay Airfield — Fighter Field #1, one of Espiritu Santo’s earliest wartime airstrips — sat right on the coast about a dozen miles north of Luganville. Built by Navy Seabees in just twenty days in mid-1942, it was operational in time to support the opening days of the Guadalcanal campaign, and by 1943 it was home to U.S. Marine Corps fighter squadrons flying the newly-arrived Vought F4U Corsair.
Turtle Bay’s most famous residents were Pappy Boyington’s “Black Sheep” of VMF-214, who trained here in the fall of 1943 before shipping out to the Solomons for the combat tour that made them legendary — 203 Japanese aircraft destroyed or damaged, nine aces, a Presidential Unit Citation, and eventually a 1970s TV show. It’s a good reminder of just how much Corsair traffic moved through this one strip during the war.
I don’t believe this wreck is from Boyington’s famous squadron, though. None of the Corsair losses documented at Turtle Bay are attributed to VMF-214 — the squadrons involved are a mix of VMF-122, VMF-225, VMF-114, VMF-111, and Marine Aircraft Group 11’s own service and headquarters squadrons. The Black Sheep’s run under Boyington was also largely over by January 1944, when he was shot down and captured.
This wreck — an intact but heavily encrusted Corsair resting on a sandy bottom a few hundred meters offshore — is almost certainly a casualty of Turtle Bay’s flight operations. First I will cover the dive itself and then deeper research into which specific plane it might be comes later in the post.
The Dive
Unlike the Coolidge, this one wasn’t a shore dive out of the Pacific Dive shore diving location. Instead, we drove up and met a small boat at a dock near Turtle Bay, which had ferried up separately from Pacific Dive’s main operation to meet us there.
There’s actually a marker buoy and downline for this wreck, tied to a block that sits roughly 20 feet in front of the plane, which itself rests at around 120 feet. Except at high tide, the buoy sits fully underwater, invisible from the surface. That was the situation at the time of day we went. It was just me and Max for this one, and once we got out to the approximate location of the dive site, the boat crew couldn’t spot the submerged buoy. So the plan, delivered with admirable directness, was essentially: “Drop down to about 100 feet, swim a contour toward the island holding that depth, and you should find it.” Not exactly GPS-precision navigation, but I’ve been through this kind of search before and enjoy the challenge of sniffing out a wreck.
We rolled off the boat and started down. Visibility was good — 40-plus feet. I’d taken a compass heading before we dropped in, and we started swimming that bearing at depth. Neither Max nor I had ever actually dived this wreck before, so this was new territory for both of us. After four or five minutes, I caught a shadow sitting a bit shallower than our depth and signaled Max. Sure enough — the Corsair.
I spent the next 10 to 15 minutes shooting photos for the photogrammetry model, working in close for the detail shots that a model needs but that don’t really convey what the whole wreck looks like at a glance.
You can explore the full interactive 3D model yourself on Sketchfab — it’s a much better way to get a sense of the wreck’s layout than any single photo.
Even doing the close, methodical work of photogrammetry mapping, it’s hard not to notice how alive the wreck has become. Dense clouds of glassfish shelter in every open cavity — the cockpit, the gap where the tail’s broken away from the fuselage, wherever there is shelter.
Here’s where it got interesting: the boat captain had mentioned there was supposedly a second airplane wreck somewhere nearby, and that if we kept swimming past the Corsair on the same heading, we might find it. We’d planned for a full hour of dive time before pickup, so we had plenty of time left to go looking. We pushed on past the Corsair for another 8 to 10 minutes, holding a contour around 100 feet, and covered somewhere north of 500 feet of open sand and reef. We saw a few shadows and some scattered rock and reef structure that got the pulse going for a second, but no second airplane.
We reversed course on the compass, swam back at a slightly different depth hoping for a different sightline, and still came up empty. If there’s a second wreck out there, it stayed hidden from us that day. It was a good reminder of how tricky underwater navigation can be, even with 40-plus feet of visibility — without a solid compass heading and a consistent depth contour, it’s very easy to swim in a slowly curving line and never realize it, especially over 500-plus feet of open sand.
We made our way back to the Corsair, and I spent the remaining time shooting wide-angle photos — the kind that actually show the whole airplane at once, which the close-in photogrammetry shots don’t.
I got a few more photos from above the wreck on my way back to the downline as we started our ascent, did a little decompression, and sent up an SMB to let the boat know we were coming up. They arrived a couple of minutes after we surfaced.
Confirming the Aircraft Type
The gull-wing shape, the “birdcage” cockpit set well back from the nose, the general proportions — this is unmistakably an F4U Corsair. Two of the online dive-site references I used for background research actually mislabel it as an “F4F Corsair,” which conflates two completely different aircraft: the F4F was Grumman’s Wildcat, not a Corsair at all. The wreck sitting off Turtle Bay is definitely a Corsair.
USMC or RNZAF?
Before I could even get to which Corsair this was, I had to sort out whose Corsair it was in the first place. I’d initially heard secondhand that this might have been a Royal New Zealand Air Force (RNZAF) aircraft, and it’s a reasonable starting theory. New Zealand flew a large Corsair force in the Pacific — thirteen RNZAF squadrons in total — several of which rotated through Espiritu Santo, and they did incur Corsair losses on this island. But every RNZAF Corsair loss I found in the accident records is logged at Palikulo Bay Airfield — the RNZAF’s main base on Santo — not at Turtle Bay.
Turtle Bay wasn’t RNZAF-free territory, though — a plane from the Royal New Zealand Avenger squadron (No. 30) was photographed sitting on the Turtle Bay strip in February 1944, apparently staging there briefly en route to Bougainville. So RNZAF aircraft clearly passed through Turtle Bay at times; they just don’t show up in the loss records there, at least not for Corsairs specifically.
Digging further, I pulled every Corsair-related accident I could find logged at or very near Turtle Bay Airfield specifically — eleven in total between mid-1943 and early 1945. Ten are U.S. Marine Corps. One, from 20 March 1944 (BuNo 17421), is logged as U.S. Navy, Headquarters Squadron — a good reminder that it’s not enough to check whether a unit operated in the general area; you have to check exactly where, and even a pattern this strong can still have exceptions. “Ten of eleven” is good evidence. It isn’t proof. Overall, I’d still call USMC the far better-supported guess for our wreck, just not an absolute certainty.
Eleven Candidates, No Confirmed Match
Wartime production demands often meant a second or third manufacturer was brought in to augment the original designer’s output, and sometimes those variants carry small physical differences — rivet patterns, panel lines, equipment fits — that can help narrow down an identification. Worth checking on any wreck like this, but here it’s a dead end: both Goodyear (FG) and Brewster (F3A) built licensed copies of the Corsair alongside Vought’s own F4U, and Goodyear-built airframes in particular are visually and functionally identical to their Vought-built F4U counterparts — same airplane, different assembly line. Several of our Turtle Bay candidates are Goodyear-built, which tells me Goodyear Corsairs were common in these squadrons by 1944, not which specific aircraft this is.
Turtle Bay, it turns out, chewed through a lot of Corsairs — and this is very likely an undercount, since it only reflects what’s made it into a searchable accident database eighty-plus years later. Using accident records from the Aviation Safety Network database, here’s every Corsair-type loss I could confirm at or immediately near Turtle Bay Airfield itself:
| Date | BuNo | Type | Unit | Notes |
|---|---|---|---|---|
| 11 Jun 1943 | — | F4U-1 | VMF-122, USMC | Near Fighter Field 1 |
| 20 Mar 1944 | 17421 | F4U-1 | U.S. Navy, Hq. Sq. | Fatal |
| 7 Apr 1944 | 56263 | F4U-1A | VMF-225, USMC | Near Turtle Bay, fatal |
| 7 Apr 1944 | 56334 | F4U-1A | VMF-225, USMC | Near Turtle Bay, same day as above |
| 3 May 1944 | 49850 | F4U-1A | USMC | |
| 13 May 1944 | 50055 | F4U-1A | USMC | Test flight, non-fatal |
| 7 Jun 1944 | 17402 | F4U-1 | VMF-114, USMC | Target towing, fatal |
| 8 Jul 1944 | 14088 | FG-1A | VMF-111, USMC | |
| 21 Jul 1944 | 14180 | FG-1 | Serv Sqd, MAG-11, USMC | Engine failure, test flight, non-fatal |
| 29 Jul 1944 | 56130 | F4U-1A | USMC | |
| 16 Jan 1945 | 57552 | F4U-1D | VMF-312, USMC | 3 mi SE of Turtle Bay, fatal, dive-bombing practice |
Two candidates still stand out as the best circumstantial fits for what the wreck actually looks like: BuNo 14180 (independently corroborated across two sources — same date, unit, location, and cause) and BuNo 50055 (nearly identical profile — non-fatal, test flight, destroyed, no combat involvement). Both fit the physical evidence well: the wreck is remarkably intact for something that’s been underwater for 80 years — fuselage, both wings, and the tail all present and roughly where they should be, not scattered the way you’d expect from a violent mid-air collision or high-speed combat loss.
I want to be clear about what eleven candidates does and doesn’t get us.
It gets us to “this was very likely a Marine Corps loss out of Turtle Bay sometime between mid-1943 and early 1945.” Our two leading candidates, BuNo 14180 and 50055, both point toward a routine test flight — non-fatal, no combat involvement, and a physical match for the largely intact wreck. A few of the other losses were also non-combat but likely resulted in messier, less intact wrecks: BuNo 17402 went down during target-towing practice with a fatality, and BuNo 57552 was lost during dive-bombing practice, also fatal.
What it doesn’t get us to is a confirmed identification. With this many losses at one small airfield over nearly two years, I doubt that’s possible without something physical from the wreck itself — a serial number, a data plate, a squadron marking — and none of that has turned up despite a good look at the cockpit and structure. I’ve seen firsthand how easy this kind of reasoning is to get wrong: my Dana Point Corsair post tells the story of correcting another team’s misidentification, built on exactly this sort of location-and-circumstance logic. So I’d rather call these “leading candidates” than dress it up as more than that.
The Missing Propeller Blades
Here’s the detail that’s bugged me the most, and I don’t have a clean answer for it.
All three propeller blade positions on the hub are completely empty as shown below — not damaged, not bent, not snapped off with a jagged stub remaining. Nothing. One blade position sits mostly exposed above the sand; the other two are low-lying or partially buried, in spots I genuinely don’t think a casual diver could access to remove a blade even if they wanted a souvenir.
A few theories, none of which fully satisfy me:
- Impact shear. Water acts almost like a solid surface when something hits it at real speed, and a spinning or windmilling propeller striking that hard can shear cleanly rather than bend or tear. It’s a real phenomenon — but shear damage is typically inconsistent between blades, not uniform, and I’d expect at least some remnant on at least one of the three. A totally clean break on all three is a tougher sell.
- Wartime salvage. Turtle Bay was an active USMC base with maintenance and supply operations close by, and this aircraft came down near shore in shallow water. A variable-pitch prop assembly was serviceable, valuable equipment. It’s entirely plausible ground crews recovered it for reuse before the airframe itself was written off and left to the reef. This is the theory I find most consistent with the evidence — a deliberate, complete removal explains “clean and total” far better than crash damage does.
- Modern souvenir removal. Possible for the one exposed blade position, much harder to credit for the two low-lying or buried ones. I did a careful visual search of the surrounding sand for scattered blade debris and came up empty — which argues against “they’re still out there nearby, just buried or out of frame,” though I can’t rule it out entirely given 80 years of storm surge and shifting sand.
I lean toward wartime salvage as the best fit for what’s actually in front of the camera, but I’m not going to pretend I’ve nailed it down. It’s a genuinely odd detail on an otherwise largely intact wreck, and I’d rather flag it plainly than force an explanation that doesn’t quite fit.
Where This Leaves Us
I’m relatively confident this is a Corsair lost by a U.S. Marine Corps squadron operating out of Turtle Bay Airfield, most likely during a non-combat test or training flight sometime between mid-1943 and early 1945. I’m not confident enough in any single accident report, out of eleven-plus documented Corsair losses at this one field, to put a name or a Bureau Number on this specific aircraft. If you’ve got access to squadron records, photos of markings from an earlier dive on this site, or anything else that might move the needle, I’d genuinely love to hear from you.
Final Thoughts
This wreck gave me pretty much everything I go looking for on a dive like this: a genuinely striking, largely intact WWII fighter resting quietly on a sandy bottom, a real hunt just to find it in the first place, and — as it turned out — a research rabbit hole afterward that ended up being as satisfying as the dive itself. I went in hoping to identify this Corsair once and for all. I came out with a much better understanding of Turtle Bay’s wartime history, a short list of strong candidates, and an honest acknowledgment that a confirmed identification may simply not be possible without something physical turning up on the wreck itself. I’m at peace with that. Not every mystery needs to be solved to be worth chasing.
The other loose thread is the second airplane wreck the boat captain mentioned — the one Max and I searched 500-plus feet for and never found. As I mentioned in the trip report, Espiritu Santo has more aircraft wreckage scattered around it than just the handful of sites divers typically visit, and this is a good example of that. I’d love another shot at finding it — with a better fix on the buoy, a bit more search time, and maybe a diver or two who’s done it before to point the way. If anyone reading this has dived a second plane wreck near Turtle Bay and knows roughly where it sits, I’d genuinely love to hear from you.
Thanks To
Pacific Dive — for making this dive happen at all, given how rarely this site gets visited, and for the logistics of getting a small boat up to Turtle Bay to meet us.
Max — for diving this one with me, being a good dive buddy on a long compass swim in search of a second wreck that stayed hidden, and being a good sport about it.
References
- Divernet — “Vanuatu: Beyond the Coolidge” — Pierre Constant’s original dive account of the wreck, including discovery details and physical description
- DiveNavigator — F4F Corsair, Vanuatu
- DivePlannerPro — Vanuatu F4F Corsair
- Wikipedia — Turtle Bay Airfield
- Wikipedia — Palikulo Bay Airfield
- Aviation Safety Network — accident record database used to compile Turtle Bay Corsair losses
- aviationarchaeology.com (AAIR) — USN accident report summaries for BuNo 13268 and BuNo 14180
- Sons of Liberty Museum — VMF-214 “Black Sheep” Squadron History
AI Transparency
I used Claude (Anthropic’s AI) to help streamline this post — sifting through historical records, cross-referencing accident data, and drafting from my research and photos. All the diving, research direction, and judgment calls are mine; Claude helped organize and refine the writing, and pushed back on a few claims that needed more evidence before I was comfortable publishing them.
