FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO96LA019 · Cessna T210L

24 Oct 1995 · College Park, MD, United States

Cessna T210L · Accident: hard landing

From Boston Logan International Airport (BOS) to an unrecorded destination

Report a problem

Event

NTSB case
BFO96LA019
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
0 · 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 T210L

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
N89EP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Boston Logan International Airport (BOS), Boston, MATo not recorded
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
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
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Aborted landing, not performed
  • Pilot in command › Recovery from bounced landing, improper

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

NTSB narrative

The pilot reported that he received an airport advisory which indicated winds were out of 240 degrees at 15 knots, with gusts to 25 knots, and the runway in use was 15. He stated that he experienced moderate to severe turbulence in the traffic pattern, so he increased his approach airspeed by 10 MPH and used only 10 degrees of flaps. The pilot stated that the airplane bounced several times during the landing. On the third bounce the nose tire blew, and the airplane veered off the runway onto the soft turf collapsing the nose gear. The pilot stated that the accident could have been avoided if he had performed a go-around when the airplane first touched down (bounced). He also stated he had encountered unexpected delays en route, and was concerned about being late for a meeting.

Probable cause

the pilot's improper recovery from a bounced landing and his failure to initiate a go-around. Related factors were the crosswind and the pilot's concern about being late for meetings he had scheduled.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO96LA019
Event ID
20001207X04653
Case number
BFO96LA019
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: d6fb47ede99611ad2d3243ee348b7d7c7ea915517e32e22dbcffec079528e8c2; retrieved 2026-09-22T23:06:51.111Z.