Piper PA22 accident near Hillsboro, Oregon, March 10, 2018
On March 10, 2018 at about 10:20 pm local time, a 1956 Piper PA22, registered N50KF, was substantially damaged in an accident during landing (landing roll) near Hillsboro, Oregon (Portland-Hillsboro airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain directional control during the landing roll in tailwind conditions.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 10, 2018 · about 10:20 pm local time · cases in 2018
- Place
- Hillsboro, Oregon · Portland-Hillsboro · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA22 150, built 1956 · all PA22s on the register
- Registration
- N50KF · registry record · serial 22-4274
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot of the tailwheel-equipped airplane reported that, during landing, the airplane ground looped, and the right main landing gear collapsed. He added that he believes he became complacent during the flight. The airplane sustained substantial damage to the fuselage. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. A review of recorded data from the automated weather observation station located on the airport reported that, about 27 minutes before the accident, the wind was from 070° at 8 knots. The airplane landed on runway 31L.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control on ground during landing (landing roll) defining event
- Landing gear collapse during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
- Personnel issues › Psychological › Personality/attitude › Complacency › Student/instructed pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation
Dual student
- Certificate: student
- Flight time: 128.6 hours in all; 53.9 in this make and model; 13.8 in the last 90 days; 2.2 in the last 30 days; 14.6 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,484.9 hours
- Last inspection: 100-hour inspection, March 5, 2018
- Maximum gross weight: 2,000 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 3,485 hours total
The flight
- Departed from: SPB Scappoose OR at 10:00 pm
- Destination: SPB Scappoose OR
- Flight plan: none
- Runway 31L, 6,600 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 070° at 8 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 61°F (16°C), dew point 37°F (3°C)
- Altimeter: 29.96 inHg
- Observation at 9:53 pm from KHIO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 1 picture from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on May 9, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Accident Photo (Courtesy of FAA) | PDF, 1 page · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N50KF the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N50KF on the register today · the tail number may have moved to another aircraft since
- Piper PA-22 Tri-Pacer and Colt 2,943 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming O-320 SERIES 27,303 aircraft carry this series today · as the NTSB recorded it
- Portland-Hillsboro Airport · nearest airport
- Scappoose Airport · departed from
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 7,004 aircraft registered
- Other NTSB records under N50KF 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/GAA18CA181.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.