FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07CA265 · Piper PA 28-140

18 Sept 2007 · Flagstaff, AZ, United States

Piper PA 28-140 · Accident: loss of control in flight during initial climb

From Flagstaff Pulliam Airport (FLG) to an unrecorded destination

Report a problem

Event

NTSB case
SEA07CA265
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 28-140

Aircraft type
Piper PA-28
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
N4764T
Operator
Aaron Parker
Onboard fatalities
Unknown
Route
From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo not recorded
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
Initial climb
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
Loss of control in flight
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 › Airspeed, not attained

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

NTSB narrative

The 33-hour student pilot was performing a short field takeoff. He selected two notches of flaps and while holding the brakes, applied full power. The airplane accelerated to 65 knots and lifted from the runway. The airspeed then decreased so the pilot pushed the nose over and retracted the flaps. He continued to descend and the airspeed would not increase. The pilot force landed the airplane off the end of the runway and it impacted trees. According to the Federal Aviation Administration inspector, there were no mechanical malfunctions with the airframe or engine. Winds at the time of the accident were from 240 degrees at 10 knots, with 16-knot wind gusts.

Probable cause

The pilot's failure to attain an adequate airspeed, which resulted in a forced landing off the end of the runway. A contributing factor to the accident was the gusting wind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07CA265
Event ID
20071024X01647
Case number
SEA07CA265
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: 67fb8415d3f83af7c3c1210dfb9f2c26b90ad09f7ab69f6e0b2480a416eb90a7; retrieved 2026-09-21T18:23:46.904Z.