ATL93LA035 · Beech 76
Marshall Air Service Beech 76 · Accident: total loss of engine power (non-mechanical) on approach
From Allegheny County Airport (AGC) to Brunswick Golden Isles Airport (BQK)
Event
- NTSB case
- ATL93LA035
- 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
- Instrument Meteorological Cond
Beech 76
- Aircraft type
- Beechcraft 76
- 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
- N38037
- Operator
- Marshall Air Service
- Onboard fatalities
- Unknown
- Route
- From Allegheny County Airport (AGC), PITTSBURG, PATo Brunswick Golden Isles Airport (BQK), Brunswick, GA
- 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 · IFR missed approach
- 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 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
- Pilot in command › In-flight planning/decision, poor
- Pilot in command › Preflight planning/preparation, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT DEPARTED ALLEGHENY AIRPORT AT 2035 EASTERN STANDARD TIME. THE PILOT RECEIVED A FULL WEATHER BRIEFING PRIOR TO THE DEPARTURE, WHICH INCLUDED A WINDS ALOFT FORECAST. HE STATED THAT HE ESTIMATED THE FUEL ON BOARD WOULD BE SUFFICIENT FOR SIX HOURS OF FLIGHT. THE PILOTS OPERATING HANDBOOK FOR THE AIRCRAFT SHOWS THE ENDURANCE FOR THE AIRCRAFT, AT THE ALTITUDE AND POWER SETTINGS USED, TO BE FIVE HOURS AND THIRTY MINUTES. THE PILOT REPORTED THAT THE AIRCRAFT WAS EXTREMELY LOW ON FUEL PRIOR TO THE ACCIDENT, AND THAT BOTH ENGINES LOST POWER PRIOR TO THE EMERGENCY LANDING ATTEMPT. THE ACCIDENT OCCURRED AT 0205 EASTERN STANDARD TIME.
Probable cause
THE PILOT'S POOR PREFLIGHT AND INFLIGHT PLANNING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA035
- Event ID
- 20001211X16120
- Case number
- ATL93LA035
- 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: 212d9db6f0ad7f4857ed7ac8bffae40f6659d34bdcec3597d8d8b58def63d75b; retrieved 2026-09-21T14:37:32.936Z.