FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22FA338 · Czech Sport Aircraft Piper Sport

8 Sept 2022 · Santa Monica, CA, United States

Czech Sport Aircraft Piper Sport · Accident: abrupt maneuver during landing

From Santa Monica Municipal Airport (SMO) to an unrecorded destination

Report a problem

Event

NTSB case
WPR22FA338
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
2 · 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

Czech Sport Aircraft Piper Sport

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
N126WK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Monica Municipal Airport (SMO), Santa Monica, CATo not recorded
Aircraft age
About 11 years (built 2011)
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 · flare/touchdown
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
Abrupt maneuver
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The flight was an introductory flight lesson for the passenger in the light-sport airplane. The route was along the Southern California Coast and the flight lasted about 35 minutes. The landing approach was uneventful, with the flight instructor providing clear indications of the airplane’s position as they flew in the traffic pattern, and declaring his intention that this would be a full-stop landing. Multiple witnesses observed the airplane land on runway 21, with one describing the landing as “hard.”

About the time of landing, a transmission over the common traffic advisory frequency (CTAF), captured a low pitch grunting sound followed by the instructor screaming, “let go, let go……. let go, let go, let go.” The grunting sound continued, and the airplane pitched aggressively nose-up and began to climb almost vertically with the engine at a high power level, before leveling off about 100-200 ft above ground level (agl), then spinning to the left, descending, and colliding with the ground.

Most of the airframe was consumed by fire; however, the postaccident examination did not reveal any evidence of preimpact mechanical malfunction or failure of the flight control system. Damage to the propeller blades indicated that the engine was producing power at impact, and the flaps were in a configuration appropriate for landing.

The airplane was equipped dual control sticks, both of which were fitted with push-to-talk (PTT) microphone switches. The instructor’s “let go” commands were transmitted over the CTAF and appeared to be coming from the background over the student’s microphone; therefore it is likely that the student pilot was holding his stick firmly, and inadvertently pressing the switch.

Federal Aviation Administration (FAA) regulations do not explicitly prohibit students, or in this case a passenger, from manipulating the flight controls during any phase of flight training; however, guidance does warn that students can be anxious learners and can be incredibly strong and often exhibit reactions that are inappropriate to the situation. The flight track indicated that along with routine flight maneuvers, the airplane did perform a series of high-bank-angle turns that would have resulted in high G-forces to the occupants. It is possible that the instructor had established a comfort level with the student after performing those maneuvers that resulted in him gaining a level of trust with the passenger’s ability.

It is common for the landing phase to be stressful for a new student, especially as the runway approaches. This stress would be further exacerbated during a hard landing, as was described by a witness. The passenger likely applied excessive aft elevator control, possibly in response to the flight instructor’s input, or as a reaction following a hard landing as described by witnesses. Given the responsive flight characteristics of the airplane, this would have resulted in the pitch up motion that exceeded the airplane’s critical angle of attack and resulted in an aerodynamic stall as observed by witnesses. Additionally, because the passenger was pressing the PTT switch, the instructor’s microphone was blocked and the passenger may not have been able to understand what the instructor was saying.

Probable cause

The pilot’s inability to maintain control of the airplane during the landing flare due to the passenger’s excessive control inputs, which resulted in the airplane exceeding its critical angle of attack and entering an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22FA338
Event ID
20220909105890
Case number
WPR22FA338
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, coordinates, cause areas. 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: bebf242e9a1dae67aa48dd8884f2a1490fecca75a8e74297656d3c0d7130b30e; retrieved 2026-09-15T07:50:42.767Z.