FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00FA064 · Cessna 172R

5 Jan 2000 · Atlantic Ocean, AO, United States

Cessna 172R · Accident: loss of control in flight en route

From Orlando Executive Airport (ORL) to Jacksonville Executive at Craig Airport (CRG)

Report a problem

Event

NTSB case
MIA00FA064
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

Cessna 172R

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
N156RA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (ORL), Orlando, FLTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, 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
Loss of control in flight
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 › Lack of recent experience in type operation
  • Pilot in command › Lack of recent instrument time

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

The noninstrument-rated private pilot was on a night solo cross-country flight at 2,600 feet in radio contact with Jacksonville approach. The airplane was subsequently observed by the controller on radar at 2,000 feet, heading 013 degrees, 112 knots at 0245:24. At 0245:57, the airplane was observed on radar at 1200 feet, heading 051 degrees, and the ground speed had increased to 124 knots. The pilot stated at 0245:58, 'I haven't any direction finder I don't see anything one six ro.' At 0246:28, radar contact was lost. The pilot had recorded as logged 1 hour of night pilot-in-command flight time. All simulated instrument time was dual instruction. The moon set at 2159 with only 1 percent illumination.

Probable cause

The pilot's lack of total experience in instrument flight, simulated instrument flight, and night flight resulting in the pilot becoming spatially disoriented, and subsequent in-flight collision with water. Contributing to the accident was the dark night with no visible horizon.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00FA064
Event ID
20001212X20403
Case number
MIA00FA064
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-01-06.
  • API snapshot SHA-256: 0a843dbf19b512c24edd4692b373f9638d9e1c09f91d6717a1f54b947fbf2e87; retrieved 2026-09-20T21:32:15.722Z.