FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC12CA040 · Cessna T210L

19 May 2012 · Whittier, AK, United States

K B Aircraft Cessna T210L · Accident: abnormal runway contact during landing

From Yakutat Airport (PAYA) to Whittier Airport (PAWR)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC12CA040
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
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
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
N732BE
Operator
K B Aircraft
Onboard fatalities
Unknown
Route Narrative disagrees
From Yakutat Airport (PAYA), Yakatat, AKTo Whittier Airport (PAWR), Whittier, AK
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
Defining eventThe 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
Abnormal runway contact
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

  • Personnel issues › Task performance

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

NTSB narrative

The pilot was landing on a short gravel runway. He did not use the prelanding checklist and failed to extend the landing gear prior to landing. The airplane sustained substantial damage to the fuselage during the gear-up landing. No preaccident mechanical malfunctions or failures were found that would have precluded normal operation.

Probable cause

The pilot’s failure use the prelanding checklist and to extend the landing gear before landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC12CA040
Event ID
20120519X31317
Case number
ANC12CA040
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-05-20.
  • API snapshot SHA-256: 2c37958103edeb274bfc54d8444760a74862de40d2ec962adac4fa5249fd0590; retrieved 2026-09-15T18:10:55.031Z.