# Accident 20020819025149A: Piper PA18, Newberg, OR, August 19, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 19, 2002, 09:35 local time
- Place: Newberg, OR
- Airport: Chehalem Airpark Airport
- Damage: Substantial damage
- Operating rules: General operating rules (Part 91)
- Location: 45.3236° N, 123.0544° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=45.3236&lon=-123.0544&mi=10
- Aircraft: N1277A, registered now (https://openairdocs.org/aircraft/N1277A) (OpenAirDocs)
- Registry model: Piper PA-18 (registry code 7101802, https://openairdocs.org/model/piper-pa-18) (OpenAirDocs)
- Registry engine: Lycoming 0-290 series (registry code 41506, https://openairdocs.org/engine/lycoming-0-290-series) (OpenAirDocs)
- Reported make and model: PIPER PA18
- NTSB investigation: [NTSB SEA02LA160](https://openairdocs.org/ntsb/SEA02LA160) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020819025149A

## Narrative

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

(.19) ON AUGUST 19, 2002, APPROXIMATELY 0935 PACIFIC DAYLIGHT TIME, A PIPER PA-18 AIRPLANE, N1277A, REGISTERED TO AND BEING FLOWN BY A PRIVATE PILOT WHO HAD RECENTLY BOUGHT THE AIRPLANE, RAN OFF THE RIGHT SIDE OF RUNWAY 25 DURING LANDING AT CHEHALEM AIRPARK (17S), NEWBERG, OREGON, AND COLLIDED WITH A WINDSOCK POLE AND A FENCE. THE AIRPLANE WAS SUBSTANTIALLY DAMAGED IN THE ACCIDENT. AT THE TIME, THE PILOT, WHO WAS QUALIFIED AND CURRENT UNDER 14 CFR 61 TO ACT AS PILOT-IN-COMMAND OF THE AIRPLANE, HAD A CERTIFICATED FLIGHT INSTRUCTOR ABOARD IN ORDER TO FULFILL AN INSURANCE POLICY PROVISION REQUIRING HIM TO ACCUMULATE 10 HOURS IN THE AIRCRAFT PRIOR TO FLYING WITHOUT AN INSTRUCTOR. NEITHER PILOT WAS INJURED. VISUAL METEOROLOGICAL CONDITIONS, WITH CALM WINDS, WERE REPORTED AT MCMINNVILLE, OREGON, AT 0953, AND NO FLIGHT PLAN HAD BEEN FILED FOR THE 14 CFR 91 INSTRUCTIONAL FLIGHT, WHICH DEPARTED STARK'S TWIN OAKS AIRPARK (7S3), HILLSBORO, OREGON, ABOUT 0915. (-23) THE PILOT HAD RECENTLY PURCHASED THE AIRCRAFT AND WAS OBTAINING 10 HOURS WITH AN INSTRUCTOR FOR INSURANCE PURPOSES. HE HAD BEEN ENDORSED FOR TAIL WHEEL OPERATIONS AND HAD ACCUMULATED 8 HOURS AT THE TIME OF THE ACCIDENT.            WHILE PRACTICING LANDINGS, THE AIRCRAFT BEGAN TO VEER TO THE RIGHT FOLLOWING A 3 POINT LANDING. THE PILOT WAS UNABLE TO REGAIN CONTROL PRIOR TO THE AIRCRAFT HITTING A FENCE AND WINDSOCK. AN INSPECTION OF THE RIGHT WHEEL BRAKE REVEALED A WARPED DISC WHICH COULD CAUSE A DRAGGING BRAKE CONDITION.

## 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 SEA02LA160](https://openairdocs.org/ntsb/SEA02LA160), Aug 19, 2002: Piper PA-18 (N1277A), Newberg, OR, substantial damage. Probable cause: A warped right brake disc resulting in a veer to the right during the landing roll, and the aircraft's subsequent collision with a fence. A contributing factor was the fence.

## Other reports on N1277A (1)

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

- [Accident 20200726009779A](https://openairdocs.org/incident/20200726009779A), Jul 26, 2020: Piper PA-18 (N1277A), Fairbanks, AK, Substantial damage. The pilot stated that on July 26, 2020 near gold king creek, Fairbanks AK (AK7), he landed his PA-18 N1277A s/n 18-1072 on an unimproved off airport grass…

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.
