What happened
The incident occurred at an airport where ground control was managing movement on the active runways and taxiways. An airport operations vehicle received clearance from the ground controller to proceed via taxiway A toward the approach end of runway 25. However, the driver of this vehicle stopped it on the taxiway without informing the controller. The reason for the stop was to catch an animal that had entered the area.
Meanwhile, the pilot of N65484 was taxiing the aircraft and performing the before takeoff checklist. During this procedure, the pilot observed the parked vehicle but did so too late to bring the aircraft to a halt in time. Consequently, the aircraft collided with the stationary airport operations vehicle.
The investigation
The investigation focused on the sequence of events leading to the collision. It was determined that the airport operations vehicle driver had deviated from standard communication protocols by stopping on an active taxiway without advising air traffic control. This lack of communication meant that other pilots, including the pilot of N65484, were unaware of the obstruction until it was too late to avoid impact.
Findings
The primary factor in this accident was the failure of the airport operations vehicle driver to communicate their position and intent to air traffic control. This resulted in a stationary obstacle on an active taxiway that was not visible to approaching aircraft until the last moment. The pilot of N65484 was performing standard pre-flight checks, which may have limited situational awareness of the immediate surroundings, but the lack of warning from the vehicle driver was the critical error. Failure to communicate position led directly to the collision.
Safety message
Airport operations vehicles must maintain constant communication with air traffic control when operating on active taxiways and runways. Any stop or deviation from the cleared route must be reported immediately to ensure the safety of all aircraft movements in the area.