FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC01LA040 · Taylorcraft 19

4 Mar 2001 · Salcha, AK, United States

Taylorcraft 19 · Accident: overrun during takeoff

From Salcha, AK to Bradley Sky-Ranch Airport (95Z)

Report a problem

Event

NTSB case
ANC01LA040
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

Taylorcraft 19

Aircraft type
Taylorcraft 19
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
N22N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salcha, AKTo Bradley Sky-Ranch Airport (95Z), North Pole, 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
Takeoff · rejected takeoff
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
Overrun
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 › Abort, delayed
  • Pilot in command › Compensation for wind conditions, inadequate

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

NTSB narrative

The private certificated pilot was departing a private airstrip in a wheel-equipped airplane. The snow-covered airstrip, oriented north/south, was 2,000 feet long, and 20 feet wide. The pilot said he began his takeoff roll toward the south, but the airplane had not become airborne by the time the airplane had traveled about two thirds of the airstrip's length. The pilot said he aborted the takeoff, but he could not stop the airplane before it went off the end of the airstrip into deep snow. The airplane nosed over and received damage to the vertical stabilizer, the rudder, the left wing lift strut, and the right wingtip. After the accident, the pilot said he noticed a 5 to 7 mph tailwind from the northeast.

Probable cause

The pilot's failure to compensate for a tailwind during takeoff, and his delay in aborting the takeoff. Factors in the accident were a tailwind, and snow-covered terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC01LA040
Event ID
20010330X00678
Case number
ANC01LA040
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, coordinates. 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: 0478e4f3333436a03b2ca273edc666a0397d66ae69ddb2cca557768ec616f25d; retrieved 2026-09-22T12:07:27.377Z.