FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA339 · Cessna 210E 210F

28 Aug 2000 · Holbrook, AZ, United States

Cessna 210E 210F · Accident: hard landing

From Dalhart Municipal Airport (DHT) to Holbrook Municipal Airport (P14)

Report a problem

Event

NTSB case
LAX00LA339
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 210E 210F

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
N210DL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Dalhart Municipal Airport (DHT), Dalhart, TXTo Holbrook Municipal Airport (P14), Holbrook, AZ
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
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 › Aircraft control, not available

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

NTSB narrative

During a porpoise and hard landing, the nose wheel collapsed and the firewall was pushed in. The pilot began to preflare about 500 feet from the landing threshold. He applied backpressure to the elevator, but nothing happened. He applied more back elevator with no effect. He began adding power about 20 feet above the runway to arrest the airplane's descent, but was still nose low. He added power to bring the nose up, but the airplane began to climb. By this time, the pilot approximated that he was 1,500 to 2,000 feet down the runway. He felt that he did not have elevator control and thought it would be too risky to attempt a go-around and approach with that condition. He elected to land, even though it would probably result in damage to the airplane. He reduced power and the airplane touched down on the nose wheel and began to porpoise. On the third bounce, the nose wheel collapsed and the airplane came to a stop on the runway. The pilot removed the rear cabin panel, and noticed that the elevator cables were loose and sagging. He checked the cables to the tail cone and noted that they appeared to be intact and connected. The post accident examination of the airplane did not reveal any mechanical anomalies that would account for the loss of elevator effectiveness. During the repair process, maintenance personnel discovered one pulley that would not move, and another pulley on the firewall exhibited scratch marks. However, they did not observe any cable or pulley wear. One of the pulleys in the elevator control system was attached to the engine firewall.

Probable cause

The lack of elevator control during final approach, for undetermined reasons, that resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA339
Event ID
20001212X21788
Case number
LAX00LA339
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: e633f0ac87c8782ad4ccd5d080aaa2795cdccc29707f6b5653d39d5be42311c0; retrieved 2026-09-22T12:30:29.806Z.