ERA22LA424 · Rockwell International 700
Rockwell International 700 · Accident: fuel exhaustion on approach
From Marianna Municipal Airport (MAI) to an unrecorded destination
Event
- NTSB case
- ERA22LA424
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Rockwell International 700
- Aircraft type
- Rockwell 700
- 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
- N700AK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marianna Municipal Airport (MAI), Marianna, FLTo not recorded
- Aircraft age
- About 43 years (built 1979)
- 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
- Approach · VFR pattern final
- 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
- Fuel exhaustion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that after about a 2-hour cross-country flight, the right engine fuel boost pump light illuminated during the final approach to the destination airport. The engine sputtered, began to lose power, and the fuel flow fluctuated between 0 to 75 pounds per hour (pph). Once the airplane reached the runway, the engine lost power completely. The pilot said he applied full left rudder to compensate for the asymmetrical thrust, but it became ineffective (likely due to the airplane’s slowing speed during the landing approach). The airplane made a hard right turn even after he reduced power to the left engine, then struck a taxiway and runway light. The pilot reported that after the airplane left the grass infield, it became airborne again. The airplane subsequently stalled and collided with two hangars, resulting in substantial damage to both wings and the fuselage. There was no postimpact fire. The pilot, numerous witnesses, and first responders to the scene reported that there was no fuel spill or smell of fuel. Examination of the airplane revealed the fuel lines to each fuel tank were impact separated from each wing and both tanks were empty of fuel. The fuel caps were secure and their respective flapper seals functioned properly. There was no evidence of a fuel leak or fuel staining anywhere on the airplane. The engine-driven fuel pumps were removed from the right and left engines and less than a drop of fuel was observed in each. The right engine was examined and no mechanical deficiencies or malfunctions were observed that would have precluded normal operation. The fuel boost pump annunciator light is activated by a pressure switch downstream of the pump. If there is no fuel pressure, the light will illuminate.
The pilot reported to the National Transportation Safety Board (NTSB) that the fuel on board the airplane at the last takeoff was 87 gallons. Fuel receipts showed that the pilot purchased about 98 gallons of fuel on the day of the accident. Later, the pilot reported that he filled both of the airplane’s wing fuel tanks to about 1 and 1/2 inches below the top of the tanks for a total of 166 gallons (83 gallons per side). However, the pilot had recently purchased the airplane and had only flown the airplane 9 times for a total flight time of 14.6 hours in the last 11 months, including the accident flight. Due to his limited experience in the accident airplane, it is possible that the pilot may have overestimated how much fuel was in the tanks. The airplane was equipped with an engine data monitor that recorded engine data for the entire flight from engine start to the time of the accident. The engine monitor indicated that the right engine was operating for about 2 hours 3 minutes and the left engine was operating for about 2 hours 4 minutes. The data for right engine showed the exhaust gas temperatures (EGT) dropping from between 1,300° to 1,400°F to about 250°F when the monitor stopped recording. The data for left engine shows the EGTs dropping from between 1,300° to 1,400°F to about 1,200° momentarily, and then less than 600°F when the monitor stopped recording. Although the drop of left engine EGTs could have been due to the pilot’s reduction of power to the left engine, the lack of any fuel in the left fuel tank with no reported fuel spill or leaks indicated that it likely sustained a complete loss of engine power soon after the right engine lost power and before the impact with the hangars. During postaccident interviews, the pilot provided varying fuel consumption numbers for fuel planning. He reported that the normal fuel flow for the airplane was 160 – 170 pph (26.6 – 28.3 gph). However, he also stated that the normal fuel flow for cruise setting was 120 - 130 pph (20 – 21.6 gph); fuel flow at full power was 170 pph (28.3 gph). Apart from the fuel flow estimates, the pilot did not provide any additional flight planning information. According to the airplane’s Pilot’s Operating Handbook (POH), a fuel flow of 160 pph during cruise flight equates to a cruise power setting of 55% power at 2,200 rpm. If the airplane was flown at that power setting during cruise flight, the airplane used about 70 gallons of fuel during the flight. Had the pilot used a 75% cruise power setting (75% power at 2,400 rpm), the fuel flow would have been about 256 pph, which would increase the fuel used during the flight to about 100 gallons. No fuel was observed on the airplane after the accident occurred and there was no evidence of any fuel spill or fuel smell. Although the pilot fueled the airplane with about 98 gallons of fuel, given the lack of fuel found at the accident site the pilot likely overestimated how much total fuel was on board the airplane at departure, which led to fuel exhaustion on the final approach. During the flare and touchdown, the pilot then failed to maintain control of the airplane and it veered off the runway, became airborne again, and stalled before it impacted the two hangars.
Probable cause
The total loss of engine power to the twin-engine airplane during final approach due to fuel exhaustion. Contributing to the accident was the pilot’s failure to maintain aircraft control during the approach to land, which resulted in a runway excursion and collision with two hangars.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA424
- Event ID
- 20220919105960
- Case number
- ERA22LA424
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, 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.
- API snapshot SHA-256: 91a7781dfa354014558353da6ebabe9f0b276f67c7d7bf3b90d5a10cd64bebe7; retrieved 2026-09-16T16:03:17.331Z.