MIA92FA158 · Cessna 172K
Rockledge Air Park Cessna 172K · Accident: loss of control in flight on approach
From River Ranch Resort Airport (2RR) to an unrecorded destination
Event
- NTSB case
- MIA92FA158
- 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
- 4 · 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
Cessna 172K
- Aircraft type
- Cessna 172
- 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
- N1196M
- Operator
- Rockledge Air Park
- Onboard fatalities
- Unknown
- Route
- From River Ranch Resort Airport (2RR), RIVER RANCH, FLTo not recorded
- 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
- Loss of control in flight
- 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
- Stall/mush
- 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(vs), not maintained
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
BEFORE THE ACCIDENT FLT DEPARTED, THE PLT OBTAINED A WX BRIEFING FOR THE RETURN FLIGHT & ADVISED THE BRIEFER THAT THERE WERE RAIN SHOWERS AT THE ARPT. THE BRIEFER ADVISED THE PLT THEY WOULD PASS THROUGH IN 30-45 MINUTES, THEN THE AREA WOULD BE CLEAR. THE PLT CALLED AGAIN, RECEIVED A WX BRIEFING & FILED A VFR FLIGHT PLAN. THE FLT DEPARTED, AND THE PLT ACTIVATED HIS FLT PLAN. THERE WAS NO FURTHER RADIO CONTACT WITH THE PLT. WITNESSES NEAR THE DESTINATION ARPT REPORTED HEARING AN ACFT MAKE TWO PASSES TO THE SOUTH ORIENTED RWY IN AN ATTEMPT TO LAND DURING THE DARK NIGHT. DURING THE THIRD APPROACH, THE ACFT STALLED & CRASHED APRX 1/4 MILE SHORT OF THE RWY. FLIGHT CONTROL CONTINUITY WAS VERIFIED. THERE WAS NO PRE-IMPACT FAILURE OR MALFUNCTION OF THE ENG. REVIEW OF THE PLT'S LOGBOOK REVEALED THAT THERE WAS A BREAK IN HIS FLYING FROM 7/24/89 TO 6/20/92. THE LAST ENTRY LOGGED WAS A NIGHT FLT ON 7/19/92. THE PREVIOUS NIGHT FLT WAS ON 7/8/89. IN THE PREVIOUS 3 YRS ONLY 1 NIGHT LANDING LOGGED AT THE DESTINATION ARPT.
Probable cause
FAILURE OF THE PILOT TO MAINTAIN ADEQUATE AIRSPEED DURING THE FINAL APPROACH RESULTING IN AN INADVERTENT STALL. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S LACK OF RECENT EXPERIENCE IN THE TYPE OPERATION, LACK OF EXPERIENCE AT THE AIRPORT IN THE TYPE OPERATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA92FA158
- Event ID
- 20001211X15470
- Case number
- MIA92FA158
- 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: fc9e3af73040498f3916977da37e53707983098c1cad2c369a91b0fde1b11724; retrieved 2026-09-21T01:00:51.125Z.