WPR12LA377 · Piper PA-28R-200
Morcom Aviation Services Piper PA-28R-200 · Accident: abnormal runway contact during landing
From First Air Field (W16) to Seattle Paine Field International Airport (PAE)
Event
- NTSB case
- WPR12LA377
- 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-28R-200
- 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
- N4922T
- Operator
- Morcom Aviation Services
- Onboard fatalities
- Unknown
- Route
- From First Air Field (W16), Monroe, WATo Seattle Paine Field International Airport (PAE), Everett, WA
- 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
- Landing
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot had recently failed the practical flight test for his commercial pilot certificate, so he and the flight instructor were scheduled to conduct several flights for the purpose of qualifying the pilot for another practical test. The two flew a dual flight, and, later that same day, the pilot conducted a solo flight in the same airplane. The next day, the flight instructor and the pilot conducted another dual flight in the accident airplane. During their departure from the origination airport, they noticed that the landing gear retraction time was unduly long, and the flight instructor remarked about it to the pilot at that time. They continued the departure, conducted some airwork, and then the pilot performed a landing at another airport. Both the pilot and the flight instructor described that landing as "hard;" however, the flight instructor reported that he had experienced harder landings in that and other airplanes. After landing, the pilots taxied the airplane back for departure, and during the climbout, the landing gear could not be retracted. They cycled the gear to no avail, left it extended, and flew back to the origination airport, where the pilot conducted an uneventful landing. Postflight examination of the airplane revealed that the wing structure near the attach point for the left main landing gear was substantially damaged. Review of the airplane maintenance records revealed that the airplane satisfactorily passed a 50-hour inspection just prior to the dual and solo flights. Review of the airplane flight log revealed that no one other than the flight instructor and the pilot flew the airplane between the inspection and the discovery of the damage. Based on the initial gear retraction anomaly and the flight instructor’s categorization of the subsequent hard landing, it is likely that that landing was not the event that caused the damage. Instead, the damage, which had to have occurred after the 50-hour maintenance inspection, likely happened the day before the damage discovery, and the hard landing during the dual flight was the event that caused the visible external manifestation of the preexisting internal wing structural damage. The fact that the same pilot who made the hard landing flew the airplane solo the day before allows for the possibility that he initiated the damage sequence during the solo flight and either did not know it or did not report it.
Probable cause
A hard landing likely made by the private pilot on a solo flight that preceded the dual instructional flight during which the wing damage became obvious.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12LA377
- Event ID
- 20120830X51133
- Case number
- WPR12LA377
- 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: e687e67a452964b09a2cc2d9546f88a1c56e6de26cd639f5232f9824dda78507; retrieved 2026-09-15T19:36:00.519Z.