FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA01LA148 · Piper PA-24-250

8 Aug 2001 · Thompson Falls, MT, United States

Piper PA-24-250 · Accident: in flight collision with object during landing

From Great Falls International Airport (GTF) to Thompson Falls, MT

Report a problem

Event

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

Piper PA-24-250

Aircraft type
Piper PA-24
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
N699WL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Great Falls International Airport (GTF), Great Falls, MTTo Thompson Falls, MT
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
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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 › Compensation for wind conditions, inadequate
  • Weather condition › Gusts

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

NTSB narrative

The pilot reported that during the flare for touch down, a sudden gust of wind lifted the left wing. The pilot applied full power in an attempt to stabilize the upset. The stall horn sounded and the aircraft drifted to the right side of the runway. The pilot was successful in stabilizing the aircraft when the left wing collided with a pine tree. The airplane touched down, collapsing the nose and left main landing gear. The airplane spun around about 180 degrees before coming to rest. The pilot reported no mechanical failures or malfunctions with the aircraft at the time.

Probable cause

The pilot's inadequate compensation in gusting wind conditions during the landing flare. A tree was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA01LA148
Event ID
20010814X01684
Case number
SEA01LA148
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-08-09.
  • API snapshot SHA-256: 9121e3ab4f095430cc24ba626cc7945eb64a8b6cf439435fed44a76ade5f5950; retrieved 2026-09-22T11:40:28.698Z.