FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA99FA075 · Cessna 210J

5 Feb 1999 · Naples, FL, United States

Cessna 210J · Accident: in flight collision with terrain/water on approach

From Everglades Airpark (X01) to Naples Municipal Airport (APF)

Report a problem

Event

NTSB case
MIA99FA075
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 210J

Aircraft type
Cessna 210
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
N6174F
Operator
Robert M. Johnson · private individual
Onboard fatalities
Unknown
Route
From Everglades Airpark (X01), EVERGLADES CITY, FLTo Naples Municipal Airport (APF)
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
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

  • Terrain condition › Water

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

NTSB narrative

The pilot contacted the tower for landing instructions 10 miles southwest of the airport. The pilot was instructed to report a 2 mile final for runway 05, and was informed to follow traffic on a midfield downwind. The pilot stated he was looking for the traffic, and asked if the traffic was over the coast. The pilot was informed the traffic was midfield base passing the tower at his 1 o'clock position. The pilot acknowledged the call and asked if he should take a left turn. The controller instructed the pilot to turn left and stated his traffic was passing from right to left at about a mile. The controller then informed the pilot to turn base, and asked if he had the traffic. The pilot stated he saw something below and asked if he had any helicopter traffic below him. The controller stated no and informed the pilot his traffic was on a right base at his 2 o'clock position. The pilot informed the controller that he did not see the traffic, and stated he needed to turn right pretty quick. The pilot was given the position of the traffic and was cleared to land. The pilot asked the controller to repeat that please. The controller informed the pilot that he was extremely low and asked if he had the traffic in sight There was no other conversation between the pilot and the controller. The airplane continued to descend out of sight.

Probable cause

In-flight collision with water while on base turn to final at night for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA99FA075
Event ID
20001205X00201
Case number
MIA99FA075
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 1999-02-06.
  • API snapshot SHA-256: 1ac3c9a124464c7883d534a062674ad8849b241b42b38eea93ee40385aaf0fb9; retrieved 2026-09-20T22:15:02.358Z.