IAD00LA045 · Beech A-36
Beech A-36 · Accident: total loss of engine power (non-mechanical) on approach
From Philadelphia International Airport (PHL) to Laurence G Hanscom Field (BED)
Event
- NTSB case
- IAD00LA045
- 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
Beech A-36
- Aircraft type
- Beechcraft A-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
- N66SB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Philadelphia International Airport (PHL), Philadelphia, PATo Laurence G Hanscom Field (BED), MA
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel management, improper
Approximate · Estimated position: the centre of Bedford, MA, the place the record names. Not the accident site.
NTSB narrative
The pilot departed on a cross-country flight with an estimated 64 gallons of usable fuel onboard. About two hours into the flight, the pilot entered the traffic pattern at the destination airport and placed the fuel selector on the left tank. While on final approach, the engine stopped producing power. The pilot switched the fuel selector to the right main tank, and momentarily turned on the fuel boost pump switch. The pilot was unable to start the engine, and landed short of the runway. The pilot reported that there should have been 12 gallons of fuel in both the left and right main wing tanks. Examination of the airplane revealed that the left main tank, left tip tank, and right tip tank were empty. Approximately 20 gallons of fuel were drained from the right main tank. No mechanical deficiencies were noted with the engine or fuel system.
Probable cause
the pilot's improper fuel management which resulted in fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD00LA045
- Event ID
- 20001212X21021
- Case number
- IAD00LA045
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: d1d9c03777cfa4b9630ce6a484ac0e64f2a6d98e96759e82829313989b8c3e4e; retrieved 2026-09-22T12:51:41.529Z.