FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA96LA098 · Consolidated-Vultee BT-13A

26 May 1996 · Brookings, OR, United States

Consolidated-Vultee BT-13A · Accident: overrun during landing

From California Redwood Coast-Humboldt County Airport (ACV) to Brookings Airport (BOK)

Report a problem

Event

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

Consolidated-Vultee BT-13A

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
N56642
Operator
Unknown
Onboard fatalities
Unknown
Route
From California Redwood Coast-Humboldt County Airport (ACV), Arcata, CATo Brookings Airport (BOK)
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 · landing roll
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 › Distance/speed, misjudged
  • Pilot in command › Go-around, not performed
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

The pilot stated that he was performing take-offs and landings in his World War II vintage aircraft. He stated that the wind direction reversed and became gusty, while he was in the traffic pattern for another landing on runway 12. The pilot elected to continue the approach and landing. He stated that when he realized he had a tail wind, it was 'too late for go-around.' He elected to veer the airplane off to one side of the runway into brush rather than continue off the opposite end of the runway and down a bluff. The right wing of the airplane impacted a fir tree. The airplane then spun around, and the left wing struck a tree stump. No preimpact mechanical deficiency was reported.

Probable cause

the pilot's misjudgment of distance/speed during the approach to landing, his failure to attain a proper touchdown point for landing, and his failure to perform a go-around, while there was sufficient runway and airspeed remaining. The tailwind was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA96LA098
Event ID
20001208X05877
Case number
SEA96LA098
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: 9e519fff7a9a0141aba7d991ed1aebbec606942c03bd2eaff7c136ca29a48c6f; retrieved 2026-09-22T22:26:32.241Z.