Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 28, 2000 · Cessna 210E 210F · N210DL

Holbrook, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 28, 2000
Injury Outcomes
No injuries (2 uninjured)
Location
Holbrook, AZ
Aircraft
Cessna 210E 210F
Tail Number
N210DL
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX00LA339

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.

NTSB Probable Cause

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

Full Narrative

On August 28, 2000, about 1550 mountain standard time, a Cessna 210E, N210DL, made a hard landing at the Holbrook, Arizona, airport. The airplane was owned and operated by the pilot under the provisions of 14 CFR Part 91. The commercial pilot and one passenger were not injured; the airplane sustained substantial damage. The personal flight departed Dalhart, Texas, about 1330 central daylight time. Visual meteorological conditions prevailed and no flight plan had been filed. The Safety Board was notified of the accident on September 21, 2000, following confirmation of the degree of damage. The pilot stated that he flew the approach as he had normally done in the past, with the landing gear extended, wing flaps partially extended, and elevator trim set at the full nose up position. He utilized power to stay on glideslope and maintained airspeed of about 85 miles per hour until short final, when he slowed to about 75 miles per hour. The pilot stated that on this approach he began to preflare about 500 feet from the landing threshold. He applied backpressure to the elevator, but stated that 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, he 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 in order to turn off the emergency locator transmitter. He 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 Federal Aviation Administration (FAA) accident coordinator examined the airplane, and reported that he did not observe any mechanical anomalies that would account for the loss of elevator effectiveness. The pilot reported that the firewall was pushed in. During the repair process, he said 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. Figure 82A of the Cessna 210 illustrated Parts Catalog illustrates the elevator control system. The Safety Board investigator examined another Cessna 210 of the same model, and observed that one of the pulleys in the elevator control system was attached to the engine firewall.

Flight

Event TypeAccident
Event Time15:50 MST
Nearest AirportHolbrook Municipal (0nm)
Runway21
Runway Length6740 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 210E 210F
Tail NumberN210DL
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · IO-520A · Reciprocating · 285
Seats6

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 71 · Third Class · Fatal

Conditions

ConditionsVMC
LightDaylight
Wind270° @ 12 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point59
Altimeter30.00 inHg
Observation Time22:56
Weather SourceWFAC

Appendix: Source Data