CHI99LA019 · Cessna 310R
Cessna 310R · Accident: loss of control in flight during landing
From Lincoln Airport (LNK) to Anaco Airport (AAO)
Event
- NTSB case
- CHI99LA019
- 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
- Unknown
Cessna 310R
- Aircraft type
- Cessna 310
- 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
- N310PB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lincoln Airport (LNK), Lincoln, NETo Anaco Airport (AAO)
- 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
- 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
- Substantial
Cause areas
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not maintained
- Pilot in command › Recovery from bounced landing, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot received reported winds of 050 to 070 degrees at 21 knots gusting to 28 knots during the approach. He reported that he '...evaluated the crosswind and determined that it was much less than expected.' At an altitude of 20 to 25 feet above the runway, the airplane '...abruptly dropped...resulting in a high bounce, another hard touchdown, with resulting bounce.' On the third touchdown the airplane remained on the runway where it groundlooped coming to rest off the runway. Maximum demonstrated crosswind component for the Cessna 310R is 19 knots. Given conditions would have produced a 16 to 26 knot crosswind.
Probable cause
the pilot's inadequate compensation for the wind conditions and the inadequate recovery from the bounced landing which resulted in a loss of control and the ground loop. Factors associated with the accident were the pilot's misjudging the winds conditions and the gusty crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA019
- Event ID
- 20001211X11223
- Case number
- CHI99LA019
- 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 1998-11-01.
- API snapshot SHA-256: aad94a1ffbc170a0c7eb243f8a0a3483e9df347daf8c48de90551073ebf2c4a0; retrieved 2026-09-22T16:24:02.912Z.