FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA98FA040 · Commander 114B

30 Nov 1997 · Cross City, FL, United States

Commander 114B · Accident: in flight encounter with weather en route

From X31 · Crystal River, FL to Tallahassee International Airport (TLH)

Report a problem

Event

NTSB case
MIA98FA040
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
3 · 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
Instrument Meteorological Cond

Commander 114B

Aircraft type
Commander 114
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
N302RS
Operator
Unknown
Onboard fatalities
Unknown
Route
From X31 · Crystal River, FLTo Tallahassee International Airport (TLH), Tallahassee, 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 · cruise
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 encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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 › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation
  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

The non-instrument rated pilot received 5 weather briefings before departing on a planned VFR flight to his destination airport. He was informed that VFR flight was not recommended, and was briefed on AIRMET information concerning marginal VFR and turbulence. The pilot departed, and while en route, he reported that he would attempt to remain below clouds at 3,500 feet msl. Later, he descended to 3,300 feet in an attempt to remain VFR. About 15 minutes later, the airplane descended slightly, then climbed to 3,700 feet. After that, the airplane entered a left descending 270 degree turn, then radar contact was lost. Subsequently, the airplane had an in-flight collision with a tree, water, and terrain. There was evidence that initial impact (with the tree) was in a left wing low, descending attitude. About 40 miles east, the Gainesvill, FL, weather was in part: 700 to 900 feet broken, 1,800 feet overcast, visibility 7 miles, wind from 240 degrees at 9 knots. No preimpact mechanical malfunction or failure of the engine or airframe was found. Review of the pilot's logbook revealed he had logged 1.1 hours of dual hooded flight and 1.7 hours of dual instrument flight.

Probable cause

VFR flight by the noninstrument-rated pilot into instrument meteorological conditions (IMC), and his failure to maintain control of the aircraft, due to spatial disorientation, which resulted in an uncontrolled descent and collision with the terrain (tree, ground & water). Related factors were: the adverse weather condition (low clouds/ceiling), and the pilot's lack of instrument experience.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA98FA040
Event ID
20001208X09215
Case number
MIA98FA040
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: a3705959aa4ce2053ca0e40efe044de35728344831bff877587fe0a8a94fab7b; retrieved 2026-09-20T22:44:52.221Z.