FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA04LA015 · Schmitt (Rotorway) Exec 162F

6 Nov 2003 · Prosser, WA, United States

Schmitt (Rotorway) Exec 162F · Accident: loss of control in flight during takeoff

From Prosser Airport (S40) to an unrecorded destination

Report a problem

Event

NTSB case
SEA04LA015
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

Schmitt (Rotorway) Exec 162F

Category
Helicopter
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
N6463S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prosser Airport (S40), Prosser, WATo not recorded
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
Takeoff
First occurrenceThe 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

  • Dual student › Collective, abrupt
  • Pilot in command(cfi) › Supervision, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While on an instructional flight, the flight instructor demonstrated a takeoff from a slope to the student pilot (owner) and then gave control of the rotorcraft to the student to execute a similar maneuver. The first attempt was aborted and the maneuver was re-initiated. On the second try the student rolled the rotorcraft to a level attitude but then failed to neutralize cyclic before attempting to liftoff. The student then abruptly applied collective and the rotorcraft began rolling left rapidly, lifting off and entering an immediate left rotation about five feet above ground. The instructor took control of the rotorcraft and attempted to regain directional control. He did not reduce throttle as the rotorcraft was over a ditch, which he did not want to land in. Without a throttle reduction the rotorcraft continued to rotate through four revolutions before RPM had decayed to an extent that sustained flight was no longer possible. The rotorcraft then touched down clear of the ditch while still rotating and immediately rolled onto its left side.

Probable cause

The student pilot's abrupt application of excessive collective and the flight instructor's inadequate supervision of the student. Contributing factors were the ditch and low rotor RPM.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA04LA015
Event ID
20031113X01898
Case number
SEA04LA015
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 03883207c2e3dbc8b0513cce20cca0882d9d89b725e90b696914c2d2a8cbaf9b; retrieved 2026-09-22T08:13:38.173Z.