Phoenix Air Flight Fenix 01
Phoenix Air Group Gates Lear JET 36A · Loss of control after fire on board
From Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD) to Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD)
Event
- NTSB case
- WPR23FA185
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- Unknown
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Gates Lear JET 36A
- Aircraft type
- Learjet 36
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N56PA
- Operator
- Phoenix Air Group
- Onboard fatalities
- Unknown
- Route
- From Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD), Oxnard, CATo Point Mugu Naval Air Station (Naval Base Ventura Co) (KNTD), Oxnard, CA
- Aircraft age
- About 47 years (built 1976)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Fire/smoke (non-impact)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
From the Wikipedia article
Phoenix Air Flight Fenix 01 was a military flight of Phoenix Air. On 10 May 2023 a serious incident occurred on this flight after a fire had broken out in flight on board a Learjet 36A and the pilots had lost control of the aircraft. The aircraft crashed into the Pacific Ocean 1.7 kilometres southwest of San Clemente Island, California. All three occupants of the Learjet died in the accident.
Accident sequence
The aircraft took off at 07:23 from Naval Base Point Mugu as the lead aircraft in formation with a second Learjet, with the callsigns FENIX01 (N56PA) and FENIX02 (N544PA). The flight headed south to San Clemente Island, with FENIX02 flying in close formation with FENIX01. The purpose of the flight was to take part in US Navy exercises in Warning Area 291 (W291). On board each aircraft were three civilian crew members.
Shortly after entering W291, at an altitude of 15,000 feet above mean sea level (MSL), the crew of FENIX02 observed the lead aircraft's flaps partially extending. They informed the crew of the lead aircraft, who acknowledged the radio call. The crew of FENIX02 then observed the flaps retracting again. Seconds later the crew of FENIX01 reported by radio an odour in the cabin. The crew of FENIX02 then reported white or grey smoke or gas rising from the rear left cabin area. In addition, an unknown liquid was observed behind the aircraft. At this point the lead aircraft was holding neither heading nor altitude.
FENIX02 noticed flames coming from the area of the aft equipment door and informed the crew of FENIX01 of the fire and of the need to declare an emergency. The crew of FENIX01 then declared an emergency and their intention to land at Naval Base San Clemente Island (NUC). FENIX02 then took over the lead of the formation flight and manoeuvred in front of FENIX01 to guide it to the airfield. FENIX02 last saw and received radio calls from FENIX01 as they descended to about 9,000 feet.
FENIX01 flew on a heading of about 165° to about 30 miles south of NUC, where the aircraft initiated a left turn. FENIX01 then flew several descending turns before it struck the water about one mile off the coast of San Clemente Island and sank in about 300 feet of water.
Investigation and cause
Cause
The National Transportation Safety Board took over the investigation into the cause of the accident. The investigators determined as the probable cause that the pilot had lost control of the aircraft as a result of a catastrophic fire that broke out on the left side of the tail section. The fire had probably originated from a leak in the left fuel line, caused by a loosening B-nut. The reason for this could not be determined from the available evidence.
Translated into English with AI assistance from the German Wikipedia article “Phoenix-Air-Flug Fenix 01” (revision 267832425, retrieved 2026-09-19) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out; the translation may contain errors, and long articles were cut to their first 700 words. Read the article
NTSB narrative
The accident airplane took off as the lead airplane in formation with a second Lear Jet airplane flying as wingman in a close formation position. The purpose of the flight was to participate in an exercise with the United States Navy in an over-water training area. Shortly after entering the training area at 15,000 ft mean sea level (msl) the wingman positioned on the right side of the accident airplane, observed the flaps on the accident airplane were partially extended. They notified the pilot of the accident airplane who acknowledged the radio call. The wingman then observed the flaps retract and observed white or gray colored “smoke or gas” coming from the left aft side of the airplane. The pilot in the accident airplane then radioed that they detected an odor in the cabin. Seconds later, the wingman observed red fluid on the underside of the tail cone followed by flames coming from around the aft equipment bay (tail cone) access door. They informed the accident pilots that their airplane was on fire and the accident pilot declared an emergency along with their intentions to land at a nearby airfield on the island. The wingman took over leading the formation and maneuvered in front of the accident airplane. The wingman last observed and heard radio transmissions from the accident airplane a short time later as they descended through about 7000 ft msl. The flight was above an overcast cloud layer that obstructed the view of the island at that time. Recorded ADS-B data showed that the accident airplane subsequently made a series of descending turns before the data ended. The airplane wreckage was located underwater about 4 miles northwest of the last ADS-B data point. The wreckage was highly fragmented, and the debris field extended several hundred feet along the ocean floor. Salvage operations were able to recover about 40 percent of the airplane wreckage. Examination of the wreckage showed areas of smoke and fire damage in portions of the airplane from the center wing fuselage outboard through the left- and right-wing roots and aft throughout the empennage. The aft equipment bay forward bulkhead, which also served as the fuselage fuel tank aft bulkhead, exhibited damage on the upper left side consistent with exposure to a focused heat source such as a fire from a leak in a pressurized fuel or hydraulic line. Additional evidence of focused fire damage was identified in the left engine pylon, which was located outboard and adjacent to the aft equipment bay. The effected area of the pylon contained engine fire detection circuits. Examination of the hydraulic shutoff valves attached to the hydraulic reservoir found that the left hydraulic shutoff valve was closed and the right valve was in the open position. The position of the left hydraulic shutoff valve indicates the aircrew likely shut down the left engine due to a fire indication (A hydraulic valve will close if the FIRE PULL tee-handle switch is activated by the flight crew in the event an engine fire is detected). Investigators were unable to determine if the witnessed flap extension and retraction was initiated by activation of the flap selector switch or induced by fire damage. The aft equipment bay houses electrical equipment capable of providing an ignition source for a fire, and hydraulic and fuel system components capable of providing fuel for a fire in the event of a leak. The left fuel motive flow line was intact from the fuel pump up to the fuselage fitting, where the line passes through the fuselage skin into the aft equipment bay near the aft left engine mount. The fuselage fitting had the stainless-steel fuel line and b-nut attached on the outboard, engine side. The inboard, aft equipment bay side of the fitting did not have an aluminum b-nut attached or the line that connects the fitting to the motive flow valve. The left engine hydraulic pressure line and PT2 line, which pass through the fuselage into the aft equipment bay adjacent to the motive fuel line, each had aluminum b-nuts present on the interior side of their respective fuselage fittings and the interior lines for each was sheared at the fitting. The left fuel motive flow fuselage fitting and the hydraulic fluid return fitting were examined. No thermal damage was observed on the outboard nuts and attached portions of tubing. Examination of the threads on the inboard side of the motive flow fitting did not exhibit evidence of thread stripping and comparison between the two fittings did not reveal any physical differences to explain why one nut remained attached and the other did not. The reason the motive flow nut was missing from the fitting could not be determined. Observed fire and heat damage patterns indicate the fire likely started in proximity to the where the pressurized fuel motive flow line connected to the firewall fitting where the missing b-nut was located. A leak from the pressurized motive flow line would have sustained and allowed an uncontrollable fire to develop. The sustained fire likely affected controllability of the airplane and resulted in the pilots’ loss of control of the airplane.
Probable cause
The pilots’ loss of airplane control following a catastrophic fire that started on the left side of the aft equipment bay (tail cone). The fire likely initiated from a leak from the left fuel motive flow line due to a b-nut that loosened for reasons that could not be determined based on available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
German Wikipedia article: Phoenix-Air-Flug Fenix 01
- Article
- Phoenix-Air-Flug Fenix 01
- Translation
- Into English with AI assistance; names of linked operators and aircraft types from Wikidata. It may contain errors.
- Revision
- 267832425 · 2026-06-10 · retrieved 2026-09-19
- Wikidata
- Q138004605
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record WPR23FA185
- Event ID
- 20230510130456
- Case number
- WPR23FA185
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- de Wikipedia article "Phoenix-Air-Flug Fenix 01" (page 13552265, revision 267832425), translated into English with AI assistance; merged with NTSB case WPR23FA185 (events / aircraft)
- Date
- NTSB record WPR23FA185: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record WPR23FA185
- Map position
- NTSB record WPR23FA185: events decimal coordinates
- Aircraft, operator and route
- NTSB record WPR23FA185: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record WPR23FA185: operated under Part 91: General Aviation
- Fatalities
- NTSB record WPR23FA185: NTSB API totalFatal
- Ground fatalities
- NTSB record WPR23FA185: events.inj_f_grnd
- Summary
- Wikipedia article lead
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "Phoenix Air Flight Fenix 01" and NTSB case WPR23FA185, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.