FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL02IA112 · Cessna 210L

30 May 2002 · Sarasota, FL, United States

Cessna 210L · Incident: wheels up landing

From Brooksville–Tampa Bay Regional Airport (BKV) to Sarasota Bradenton International Airport (SRQ)

Report a problem

Event

NTSB case
ATL02IA112
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
Incident
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
0 · all aircraft and ground
Ground fatalities
Unknown
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
Charter & commuter
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 210L

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
N7PJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Brooksville–Tampa Bay Regional Airport (BKV), Brooksville, FLTo Sarasota Bradenton International Airport (SRQ), SARASOTA/BRADEN, 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 135: Air Taxi & Commuter
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
Landing · flare/touchdown
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
Wheels up landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Pilot in command › Checklist, not followed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, on downwind he put the landing gear handle into the down and locked position. He did not recall if he had a down and lock indication light. Upon touchdown, the landing gear retracted and the airplane collided with the ground. Examination of the airplane revealed that the landing gear was in the up and locked position, and that there were no mechanical discrepancies found. The Cessna 210, before landing checklist states in part that the landing gear should be extended and that the pilot should visually observe that the main gear is down and that the green indicator light is on. The registered owner and pilot were requested to complete a pilot/operator report but have not responded.

Probable cause

The pilot's failure to follow the before landing checklist and confirm that the landing gear was extended.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL02IA112
Event ID
20020607X00826
Case number
ATL02IA112
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, coordinates. 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: 5fe94c7282a2e805a87457dc54c49f4d903fdd6023cd0420f4de80c2164a266f; retrieved 2026-09-18T16:02:31.707Z.