37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1177654 |
Time | |
Date | 201406 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Baron 55/Cochise |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Person 1 | |
Function | Airport Personnel Vehicle Driver |
Experience | Flight Crew Last 90 Days 0 Flight Crew Total 0 Flight Crew Type 0 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 30 Vertical 50 |
Narrative:
As operator of a maintenance vehicle; I entered runway 31 from the intersection with a short taxiway; letter unknown; leading from the terminal ramp. I failed to see a beechcraft baron 55 twin engine landing on runway 31 after an abbreviated visual check as I approached the runway from the ramp.I did not hear communications from the aircraft as the airband radio mounted in the vehicle was not operating. This was discovered while clearing the vehicle access gate onto the ramp and I proceeded without the radio in operation. My warning beacon on the vehicle roof was operating normally.I did a visual check downwind as I approached the short taxiway connecting the ramp to runway 31 and failed to see the baron on its final approach. I can only speculate it must have been very close to touching down; or already wheels-down as I pulled into its path.my first awareness of the aircraft was a shortened roar of engines as it passed slightly in front of and over my vehicle. I was approximately mid-point and nearing the centerline of the runway; moving at about 30 mph. After a startled; reflexive duck I saw it by craning my head out the open driver side window. The baron was gear up and accelerating hard to avoid my vehicle.after seeing the baron circling for a second attempt; I turned around from the ASOS site and returned to the ramp after it had landed and pulled up to the fueling point. I exchanged information with the pilots and airport manager. After this exchange; I departed the airport to return to my home station.multiple failures on my part led to this event. Distraction played a part as did lack of situational awareness. This is a quiet airport and we can grow complacent; this leads to bad choices. I did not stop fully at the hold line short of runway 31 and perform a proper visual check for a non-towered aoa. Had I done so; I would in all likelihood have seen the baron already on the ground and rapidly approaching my position. This is the key failure and only fast and accurate reaction by the pilot avoided a serious accident.
Original NASA ASRS Text
Title: A quick rejected landing and go-around by the flight crew of a Beech Baron averted a likely collision with the reporter's maintenance vehicle when he pulled onto the runway without a thorough scan of the pattern and without a functioning radio to monitor CTAF transmissions at the uncontrolled airport.
Narrative: As operator of a maintenance vehicle; I entered Runway 31 from the intersection with a short taxiway; letter unknown; leading from the terminal ramp. I failed to see a Beechcraft Baron 55 twin engine landing on Runway 31 after an abbreviated visual check as I approached the runway from the ramp.I did not hear communications from the aircraft as the airband radio mounted in the vehicle was not operating. This was discovered while clearing the vehicle access gate onto the ramp and I proceeded without the radio in operation. My warning beacon on the vehicle roof was operating normally.I did a visual check downwind as I approached the short taxiway connecting the ramp to Runway 31 and failed to see the Baron on its final approach. I can only speculate it must have been very close to touching down; or already wheels-down as I pulled into its path.My first awareness of the aircraft was a shortened roar of engines as it passed slightly in front of and over my vehicle. I was approximately mid-point and nearing the centerline of the runway; moving at about 30 MPH. After a startled; reflexive duck I saw it by craning my head out the open driver side window. The Baron was gear up and accelerating hard to avoid my vehicle.After seeing the Baron circling for a second attempt; I turned around from the ASOS site and returned to the ramp after it had landed and pulled up to the fueling point. I exchanged information with the pilots and airport manager. After this exchange; I departed the airport to return to my home station.Multiple failures on my part led to this event. Distraction played a part as did lack of situational awareness. This is a quiet airport and we can grow complacent; this leads to bad choices. I did not stop fully at the hold line short of Runway 31 and perform a proper visual check for a non-towered AOA. Had I done so; I would in all likelihood have seen the Baron already on the ground and rapidly approaching my position. This is the key failure and only fast and accurate reaction by the pilot avoided a serious accident.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.