SEA91LA093 · Aeronca 7BCM
Aeronca 7BCM · Accident: on ground/water collision with object while standing
From an unrecorded airport to Sanderson Field (SHN)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- SEA91LA093
- 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
- 0
- 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
Aeronca 7BCM Possible conflict
- Aircraft type
- Aeronca 7
- 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
- N81578
- Operator
- Michael A. Perdue · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Sanderson Field (SHN), Shelton, 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
- Standing · engine(s) start-up
- 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
- On ground/water collision with object
- 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
- Pilot in command › Starting procedure, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT THE BEGINNING OF A FLIGHT, THE PILOT REPORTED THAT HE HAD PLACED CHOCKS IN FRONT OF THE MAIN LANDING GEAR AND RETURNED TO THE COCKPIT TO TURN ON THE FUEL. THE PILOT THEN PROCEEDED TO THE PROPELLER TO PULL THE ENGINE THROUGH. AS THE PILOT TURNED THE PROPELLER, THE ENGINE STARTED AT A HIGH RPM AND THE AIRCRAFT JUMPED THE CHOCKS. THE PILOT TRIED TO HANG ONTO THE RIGHT WING AS IT SWUNG AROUND ONCE, MISSING THE FUEL PUMPS AND A PARKED PIPER. THE AIRCRAFT CAME AROUND FOR THE SECOND TIME AND COLLIDED INTO THE RIGHT SIDE OF THE PIPER.
Probable cause
THE PILOT USED INADEQUATE STARTING PROCEDURES. FACTORS TO THE ACCIDENT WERE: THE PILOT DID NOT USE PROPER ASSISTANCE AND THE PASSENGER'S INADVERTENT CONTROL INTERFERENCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA91LA093
- Event ID
- 20001212X16893
- Case number
- SEA91LA093
- 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. 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: 9af296864ccc4e615c8cd7569ab9482d4d83d2991f1da109286b93c4a8ae3d59; retrieved 2026-09-23T04:18:17.882Z.