MIA93FA180 · Glasair SH-2F
Glasair SH-2F · Accident: loss of engine power on approach
From LaGrange Callaway Airport (LGC) to Orlando Executive Airport (ORL)
Event
- NTSB case
- MIA93FA180
- 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
- 2 · 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
Glasair SH-2F
- Aircraft type
- Glasair 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
- N87CK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From LaGrange Callaway Airport (LGC), LA GRANGE, GATo Orlando Executive Airport (ORL), Orlando, FL
- 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 turn to base
- 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
- Loss of engine power
- 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; Stall
- 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
- Pilot in command › Airspeed(vso), not maintained
- Pilot in command › Fuel tank selector position, improper
Approximate · Estimated position: the centre of Ocala, FL, the place the record names. Not the accident site.
NTSB narrative
The airplane was observed by a witness on downwind. The engine was heard backfiring. Another witness observed the airplane at about 200 feet agl, and the fuselage was moving back and forth from left to right. The airplane was very slow with a slight nose-up attitude. The airplane rolled right, nosed over, and disappeared from view before colliding with the terrain. The airplane was destroyed. The private pilot and one passenger were fatally injured. The fuel selector pointer was found positioned halfway between the main fuel tank position and the header tank position.
Probable cause
THE PILOT-IN-COMMAND'S FAILURE TO MAINTAIN AIRSPEED (VSO) DURING A FORCED LANDING, RESULTING IN AN IN-FLIGHT LOSS OF CONTROL (STALL), AND SUBSEQUENT IN-FLIGHT COLLISION WITH TERRAIN. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT-IN-COMMAND'S IMPROPER POSITIONING OF THE FUEL TANK SELECTOR VALVE RESULTING IN FUEL STARVATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA93FA180
- Event ID
- 20001211X13191
- Case number
- MIA93FA180
- 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: 662247621093906ad8899d8396801e790ce4a5899493893ee64ef1147a0d6010; retrieved 2026-09-21T00:25:10.153Z.