FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21FA283 · SIAI-Marchetti SM-1019B

24 Jul 2021 · Lewiston, ID, United States

Jackson 50 SIAI-Marchetti SM-1019B · Accident: loss of control in flight during initial climb

From an unrecorded airport to Hungry Ridge Ranch Airport (37ID)

Report a problem

Event

NTSB case
WPR21FA283
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
1 · 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

SIAI-Marchetti SM-1019B

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
N28U
Operator
Jackson 50
Onboard fatalities
Unknown
Route
From not recordedTo Hungry Ridge Ranch Airport (37ID), Grangeville, ID
Aircraft age
About 44 years (built 1977)
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
Initial climb
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
Loss of control in flight
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
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was attempting an intersection takeoff about midfield when, shortly after the airplane became airborne, it pitched up aggressively, rolled left, and descended into the ground in a nose-down attitude.

Examination did not reveal any evidence of preaccident malfunctions or failures of the flight control system, and there was no evidence to indicate that the pilot’s seat had moved. Both the engine and propeller exhibited damage signatures consistent with high engine power at impact.

The airplane was equipped with a flight control locking system that comprised a pivoting, U-shaped control lock tube mounted permanently to the rudder pedal assembly and a forward-facing locking arm mounted to the pilot’s control stick. The control lock immobilized the aileron and elevator controls but still allowed for near-full movement of the rudder and tailwheel.

The cabin floor, where the control lock tube should have been mounted for flight, was severely deformed and compressed. Had the lock been stowed during impact, it would have been pinned under the flight control stick, crushed longitudinally, and its retaining clip would have been deformed; however, the control lock and its retaining clip were essentially undamaged, and the lock was found raised off the floor. The locking arm on the control stick also showed no evidence of deformation or impact damage but had rotated about 90° to the right of its normal position, as if forced into that position on impact while the control lock was still attached.

Given this information, it is likely that the control lock was installed on the flight control stick during takeoff and impact. High-resolution security camera footage of the accident revealed no discernable movement of the elevators or ailerons, further suggesting that the flight controls were immobilized by the control lock.

Although the control lock is painted red, its orientation when engaged results in the pilot viewing it directly down its length, at its narrowest profile. A pilot who owned a similar airplane stated that he had once become distracted during preflight checks and was able to taxi, initiate takeoff, and become airborne with the control lock engaged. He stated that, once he realized his mistake, removal of the lock was a struggle due to the forces imposed on the control stick during takeoff.

The pitch trim was found in an almost full nose-down position, suggesting that the pilot may have been attempting to use the trim to arrest the airplane’s increasing nose-up attitude due to the locked control stick. Whether the pilot recognized that the control lock was engaged or believed he had a flight control problem could not be determined. Regardless, after takeoff during a dynamic and transitional phase of flight, there would have been minimal time to accurately diagnose the issue and disconnect the control lock.

The intended purpose and destination of the flight was routine and there was no apparent time pressure present. The pilot was reported to be extremely thorough about performing preflight checks, and according to his wife, the expected duration of his normal preflight activities would not have allowed him to depart when he did. The pilot had limited experience in the accident airplane, which could explain why he did not remove the control lock during the preflight inspection. There was no video evidence to provide insight into the duration and scope of the pilot’s preflight inspection; however, omission of the preflight control check was uncharacteristic given his extensive flight experience, and the reason it was not performed could not be determined. While omission of the control check is consistent with a pilot rushing or distracted, and the short duration from taxi to takeoff would have reduced this pilot’s opportunity to detect his error, the investigation was not able to determine the reason it was not performed. Had the pilot completed a functional check of the controls before initiating takeoff, the presence of the lock would have been detected and the accident would have been prevented.

Although the pilot’s autopsy demonstrated the presence of heart disease, which posed an increased risk of an impairing or incapacitating cardiac event, heart disease is unlikely to have caused inattention. It is also unlikely that the pilot was incapacitated by a cardiac event because his final radio transmission showed that he was aware and speaking after the onset of loss of control. Thus, it is unlikely that the pilot’s heart disease contributed to the accident.

Probable cause

The pilot’s failure to remove the flight control lock before departure, which resulted in a loss of airplane control and impact with terrain. Contributing to the accident was his failure to perform an adequate preflight inspection and flight control check before takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21FA283
Event ID
20210725103534
Case number
WPR21FA283
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, 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: d26aed34e754c5649dcfb313fb2bc1d60bbcb849897ce63ea49a3ba3b2c6b414; retrieved 2026-09-15T07:32:14.165Z.