SEA92LA193 · Cessna 172N
Cessna 172N and Lamb/Starduster SA300 · Accident: on ground/water collision with object while taxiing
Event
- NTSB case
- SEA92LA193
- 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
Aircraft 1 · Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N737TK
- Operator
- Wings Aloft
- Onboard fatalities
- Unknown
- Route
- From Harvey Field (S43)To King County International Airport - Boeing Field (BFI), Seattle, 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
- Taxi · to runway
- 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
- Destroyed
Aircraft 2 · Lamb/Starduster SA300
- Aircraft type
- Lamb/starduster SA300
- 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
- N548CL
- Operator
- Rosenfield, John W. · private individual
- Onboard fatalities
- Unknown
- Route
- From Skykomish State Airport (S88), Arlington, 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
- Landing · landing roll
- 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
- Destroyed
Cause areas
- Pilot in command › Visual lookout, not maintained
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT OF THE CESSNA TAXIED HIS AIRCRAFT THROUGH THE INTERSECTION OF THE TURF RUNWAY (RWY 31) AT THE UNCONTROLLED AIRPORT DURING WHICH HE COLLIDED WITH THE STARDUSTER WHICH WAS ROLLING OUT FOLLOWING LANDING. THE PILOT OF THE CESSNA REPORTED THAT HE HAD OBSERVED THE TURF RUNWAY CROSSING CAUTIONARY SIGN AND ADMITTED TO THE INTERVIEWING FAA INSPECTOR THAT HE HAD NOT CLEARED THE INTERSECTION FOR ANY POSSIBLE LANDING TRAFFIC PRIOR TO ENTERING. ALTHOUGH THE PILOT OF THE CESSNA INDICATED THAT THE AIRCRAFT RADIO WAS OPERATING ON THE LOCAL UNICOM FREQUENCY, HE REPORTED THAT HE NEVER HEARD ANY TRANSMISSION FROM THE STARDUSTER. A FLIGHT INSTRUCTOR AND STUDENT REPORTED HEARING THE PILOT OF THE STARDUSTER ANNOUNCE HIS ENTRY INTO THE PATTERN, AS WELL AS A CALL TO BASE TURN AND FINAL. THE STARDUSTER PILOT REPORTED NEVER SEEING THE CESSNA UNTIL IMMEDIATELY BEFORE THE COLLISION.
Probable cause
THE PILOT IN COMMAND'S FAILURE TO MAINTAIN ADEQUATE VISUAL LOOKOUT. FACTORS CONTRIBUTING TO THE ACCIDENT WERE THE PILOT IN COMMAND'S POOR VFR PROCEDURES AND HIS INADEQUATE MONITORING OF THE UNICOM FREQUENCY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA193
- Event ID
- 20001211X15550
- Case number
- SEA92LA193
- 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: 920ea06bfeec644028e24a95078f301482183ddad407a46172a5e201b7ab8dee; retrieved 2026-09-23T02:42:19.036Z.