FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA575 · Piper PA28 140

29 Sept 2018 · Spokane, WA, United States

Piper PA28 140 · Accident: collision during takeoff/landing on approach

From Felts Field (SFF) to Fowlers Northwest 40 Airport (12WA)

Report a problem

Event

NTSB case
GAA18CA575
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 PA28 140

Aircraft type
Piper PA28
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
N40825
Operator
Unknown
Onboard fatalities
Unknown
Route
From Felts Field (SFF), Spokane, WATo Fowlers Northwest 40 Airport (12WA), Cheney, WA
Aircraft age
About 44 years (built 1974)
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
Approach · VFR go-around
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
Collision during takeoff/landing
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The noninstructor-rated pilot reported that he agreed to go flying with a student pilot in the student's airplane and act as pilot-in-command while seated in the right seat. During the approach to land with the student on the controls, the airplane was high, but with the "airfield made," the student selected full flaps. According to the pilot, the airplane "got slow and low," and the student initiated a go-around, during which, in a single motion, the pilot raised the flaps to the full-up position, and the airplane "struggled to fly and climb." Subsequently, the airplane impacted trees at the end of the runway and came to rest on its right side.

The pilot added that the Pilot's Operating Handbook states that the flaps should be retracted one notch at a time.

The airplane sustained substantial damage to both wings, the fuselage, and the empennage.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The pilot’s improper retraction of the flaps during a go-around, which resulted in the airplane’s failure to climb and its subsequent collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA575
Event ID
20181003X55231
Case number
GAA18CA575
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: 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: bde0a80bc82f99abca6301c76aeb0d5b36ae0bcc1b9f32c67ad0563a8a0b9335; retrieved 2026-09-16T08:18:07.276Z.