ATL93LA128 · Brown GLASSAIR SH-2 GLASSAIR
Brown GLASSAIR SH-2 GLASSAIR · Accident: total loss of engine power (non-mechanical) on approach
From Charlotte-Monroe Executive Airport (EQY) to Huggins Memorial Airport (58J)
Event
- NTSB case
- ATL93LA128
- 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
Brown GLASSAIR SH-2 GLASSAIR
- Aircraft type
- Brown GLASSAIR SH-2
- 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
- N412NV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charlotte-Monroe Executive Airport (EQY), Monroe, NCTo Huggins Memorial Airport (58J)
- 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 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
- Fluid, fuel › Exhaustion
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT THE ENGINE STARTED RUNNING ROUGHLY WHILE ON APPROACH TO RUNWAY 32. BECAUSE HE WAS TOO HIGH FOR A SAFE TOUCHDOWN AND ROLLOUT, THE PILOT ATTEMPTIED A FORCED LANDING TO A FIELD ADJACENT TO THE AIRPORT. DURING THE FORCED LANDING, THE AIRPLANE WAS DAMAGED. THE EXAMINATION OF THE AIRPLANE AND ACCIDENT SITE DISCLOSED THAT THERE WAS NO FUEL IN THE FUEL TANKS NOR WAS THERE FUEL SPILLED IN THE IMMEDIATE VICINITY OF THE MAIN WRECKAGE. THE AIRPLANE WAS LAST REFUELED THREE WEEKS PRIOR TO THIS FLIGHT, AND HAD FLOWN ABOUT TWO HOURS PRIOR TO THIS FLIGHT. THE PILOT ESTIMATED A TOTAL FUEL ENDURANCE OF FOUR AND ONE HALF HOURS; THE FUEL GUAGE INDICATED ABOUT 22 GALLONS OF FUEL ON BOARD AT HIS LAST DEPARTURE. THE PILOT ALSO REPORTED THAT, N412NV HAD A HISTORY OF VENTING LARGE QUANTITIES OF FUEL WHILE PARKED ON THE RAMP. ACCORDING TO THE PILOT, STODDARD-HAMILTON (GLASSAIRE), ISSUED A SERVICE BULLETIN TO CORRECT THE FUEL VENTING PROBLEM; THE SERVICE BULLETIN HAD NOT BEEN ACCOMPLISHED ON N421NV.
Probable cause
THE PILOT'S INADEQUATE FUEL PLANNING WHICH RESULTED IN THE EXHAUSTION OF THE FUEL SUPPLY AND THE LOSS OF ENGINE POWER. A FACTOR WAS THE PILOT'S FAILURE TO COMPLY WITH A MANUFACTURER'S SERVICE BULLETIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA128
- Event ID
- 20001211X12770
- Case number
- ATL93LA128
- 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: e73df8a7875fc73f1b01e9560dedd2744e4a61f48334efcf1496bef177436793; retrieved 2026-09-21T22:52:33.713Z.