FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA93FA184 · REHER, Kent O. RV 6

27 Aug 1993 · Grand Ridge, FL, United States

REHER, Kent O. RV 6 · Accident: in flight collision with terrain/water en route

From Mobile Regional Airport (MOB) to Pompano Beach Airpark (PMP)

Report a problem

Event

NTSB case
MIA93FA184
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
1 · 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

REHER, Kent O. RV 6

Aircraft type
Reher Kent RV-6
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
N220KM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mobile Regional Airport (MOB), Mobile, ALTo Pompano Beach Airpark (PMP), Pompano Beach, 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
En route · descent
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
In flight collision with terrain/water
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

  • Reason for occurrence undetermined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Pilot reported to ATC that he was descending from 13,500 feet to 11,500 feet. When passing 11,500 feet the pilot reported he was descending to 9,500 feet. No further communication was made with the pilot. Radar data showed the aircraft descended normally until passing 10,000 feet. At that point the aircraft descended rapidly and was lost from radar at 5,200 feet. Eyewitnesses observed the aircraft in normal flight at about 10,000 feet. The aircraft's wing rocked back and forth and the aircraft then nosed over and descended vertically with the engine operating at high rpm until ground impact. Postcrash examination of the aircraft revealed all components necessary for flight were located on or around the main wreckage. No evidence to indicate precrash failure or malfunction of the aircraft structure, flight controls, or engine was found. No evidence of in-flight bird contact was found. The aircraft kit manufacturer reported that he has not seen any stability or control problems that would cause uncontrolled vertical descent. The pilot was reported to be in good health and good spirits before the flight.

Probable cause

UNDETERMINED.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA93FA184
Event ID
20001211X13194
Case number
MIA93FA184
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: 420f38f65cbad237f1a05a4121d22ba59c32d0bfc36b5e77ceef10b0e92fcd76; retrieved 2026-09-21T00:24:39.410Z.