FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13LA223 · Schweizer Aircraft Corp G-164B

9 May 2013 · Biggs, CA, United States

Williams Ag Service Schweizer Aircraft Corp G-164B · Accident: runway incursion (vehicle, aircraft or person) during landing

From Yuba County Airport (MYV) to Priv · Biggs, CA

Report a problem

Event

NTSB case
WPR13LA223
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
1
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

Schweizer Aircraft Corp G-164B

Aircraft type
Schweizer G-164
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
N8214S
Onboard fatalities
Unknown
Route
From Yuba County Airport (MYV), Marysville, CATo Priv · Biggs, CA
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
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
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Personnel issues › Psychological

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

NTSB narrative

The pilot reported that, while in the traffic pattern for landing, he was told by ground operations personnel that maintenance was being performed on the runway. The pilot scanned the area and saw trucks parked on the south end of the airstrip property but nothing on the runway. The pilot continued the landing, and taxied the airplane down the runway after landing. Although the pilot was performing s-turns for visibility purposes, he did not see service equipment on the runway, and the airplane collided with it and the operator of that equipment. The operator, who was fatally injured, was pushing a blower down the center of the runway and was wearing hearing protection at the time of the collision. It is likely that, due to the hearing protection and the sound of the blower, the operator did not hear the airplane. Postaccident examination of the airplane revealed minor damage to both the inlet scoop and the lower right wing lower surface.

Probable cause

The pilot’s failure to adequately monitor the runway environment during taxi, which resulted in an on-ground collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13LA223
Event ID
20130509X04822
Case number
WPR13LA223
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. 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: fc104edb1710b47b1536601a5669d5cb1202f616681898ee56b5163c47e8cddf; retrieved 2026-09-13T18:01:05.937Z.