SEA93LA067 · Beech C-99
Ameriflight Beech C-99 · Accident: on ground/water collision with object while standing
From an unrecorded airport to 75S · Burlington, WA
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
- SEA93LA067
- 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
Beech C-99 Narrative disagrees
- Aircraft type
- Beechcraft C-99
- 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
- N63978
- Operator
- Ameriflight
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 75S · Burlington, 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) operating
- 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 of other aircraft › Starting procedure, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT, HAVING JUST LANDED HIS AERONCA ON RUNWAY 31L, EXITED AT THE FIRST TAXIWAY AND WAS CLEARED BY GROUND CONTROL TO HIS DESTINATION ON THE AIRPORT. NO REQUEST BY THE AERONCA PILOT WAS MADE AS HE APPROACHED AND PASSED BEHIND THE BEECH C-99 WHICH WAS EXECUTING A RUNUP AT A HOLD SHORT. AS THE AERONCA PASSED BEHIND THE BEECH IT SPUN AROUND AND ITS ENGINE QUIT. THE PILOT OF THE AERONCA THEN RADIOED GROUND CONTROL THAT HE HAD BEEN SPUN AROUND AND GROUND CONTROL REQUESTED THE BEECH TO 'COME TO IDLE' WHICH WAS ACKNOWLEDGED. THE PILOT OF THE AERONCA THEN EXITED HIS AIRCRAFT TO HAND PROP THE ENGINE. ONCE THE ENGINE STARTED, THE AIRCRAFT BEGAN TAXIING WITHOUT ANY OCCUPANTS AS THE PILOT HAD LEFT THE THROTTLE IN A POSITION GREATER THAN IDLE. THE AERONCA SUBSEQUENTLY IMPACTED THE RIGHT REAR QUARTER OF THE BEECH.
Probable cause
THE IMPROPER STARTING PROCEDURE BY THE PILOT OF THE AERONCA. A FACTOR CONTRIBUTING TO THE ACCIDENT WAS INADEQUATE COMMUNICATIONS BY THE PILOT OF THE AERONCA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93LA067
- Event ID
- 20001211X11892
- Case number
- SEA93LA067
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1993-02-25.
- API snapshot SHA-256: 805467d0dd7ea98f0fce6869a381c10782341a53be4bdd021b85b401d6b8c858; retrieved 2026-09-23T02:18:10.161Z.