FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC09CA085 · Cessna 140

19 Aug 2009 · Fairbanks, AK, United States Possible conflict

Cessna 140 · Accident: landing area overshoot

From Fairbanks, AK to Fairbanks, AK

Report a problem

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

Event

NTSB case
ANC09CA085
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 140

Aircraft type
Cessna 140
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
N72518
Operator
Ajmi Amal R
Onboard fatalities
Unknown
Route
From Fairbanks, AKTo Fairbanks, 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
Landing area overshoot
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The solo private pilot was landing a tailwheel-equipped airplane on a mountaintop airstrip at the completion of a Title 14, Code of Federal Regulations Part 91 personal flight. She reported that while landing, she inadvertently touched down beyond her intended touchdown point. Realizing she would be unable to stop the airplane before reaching the end of the airstrip, she said she applied heavy braking at the end of the landing roll, but the airplane continued off the end of the airstrip and nosed over. The airplane sustained substantial damage to the left wing, left wing lift strut, and empennage. The pilot said there were no preaccident mechanical problems with the airplane.

Probable cause

The pilot's failure to achieve a proper touchdown point, resulting in an overrun and a nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC09CA085
Event ID
20090821X51934
Case number
ANC09CA085
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-08-20.
  • API snapshot SHA-256: d3bdd55e23c256677a1dc025f23e1475bd1824e92395ca026698e01f2a3f8a97; retrieved 2026-09-15T12:49:36.585Z.