# Accident 20030907035159A: Piper PA18150, Tok, AK, September 7, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 7, 2003, 12:00 local time
- Place: Tok, AK
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Operator: FMAA
- Location: 64.9167° N, 142.4500° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=64.9167&lon=-142.4500&mi=10
- Aircraft: N8597D, registered now (https://openairdocs.org/aircraft/N8597D) (OpenAirDocs)
- Registry model: Piper PA-18-150 (registry code 7101828, https://openairdocs.org/model/piper-pa-18-150) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA18150
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 7,500 total, 1,000 in this make and model, 250 in the last 90 days
- NTSB investigation: [NTSB ANC03CA110](https://openairdocs.org/ntsb/ANC03CA110) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030907035159A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ^PRIVACY DATA OMITT^ LANDED ON RIDGE TOP, FRONT SEAT ONLY OCCUPIED, RUNWAY ROUGH, APPLIED BRAKES, ALLOWED TAIL TO RISE TOO HIGH ANGLE, AIRCRAFT NOSED OVER ONTO ITS BACK.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ANC03CA110](https://openairdocs.org/ntsb/ANC03CA110), Sep 7, 2003: Piper PA-18-180 (N8597D), Eagle, AK, substantial damage. Probable cause: The pilot's selection of an unsuitable landing area, and his excessive use of the airplane's brakes during the landing roll, resulting in a nose over. A factor associated with the accident was rough…

## Other reports on N8597D (5)

Matched to the same aircraft by N-number and date.

- [Incident 20110827019019I](https://openairdocs.org/incident/20110827019019I), Aug 27, 2011: Piper PA-18-150 (N8597D), Tok, AK, Minor damage. Ptrs#AL01201102955UPON takeoff from Tok, AK. Airport, the propeller lost 6 inches of one blade. Pilot made emergency landing on Alaska highway.
- [Accident 20060816017959A](https://openairdocs.org/incident/20060816017959A), Aug 16, 2006: Piper PA18150 (N8597D), Tok, AK, Substantial damage. (-23) Airman stated that on liftoff from a remote ridge line a 10 knot left crosswind caused him to drift to the right and the right wing struck a tree…
- [Accident 20040826018809A](https://openairdocs.org/incident/20040826018809A), Aug 26, 2004: Piper PA18150 (N8597D), Johnson River, AK, Substantial damage. (-23) [privacy data omitted] during a landing at a bush strip the aircraft hit a rock collapsing the right gear leg. The right wing struck the ground causing…
- [Accident 19940902025489A](https://openairdocs.org/incident/19940902025489A), Sep 2, 1994: Piper PA18 (N8597D), Tok, AK, Substantial damage. Settled after early liftoff from remote strip. Camshaft 40 percent worn. Prior metal in screens. Poor maintenance.
- [Accident 19860611036352A](https://openairdocs.org/incident/19860611036352A), Jun 11, 1986: Piper PA18 (N8597D), Fairbanks, AK, Substantial damage. During climb right wing and gear struck N96320 in float and propeller. Flipped over landing on a sand bar in river.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.