A PA31 pilot making a night takeoff from YIP experienced a conflict with a ground vehicle which failed to exit the runway.

2010-07 · NASA ASRS report 896396

Date: 2010-07 · Aircraft: PA-31 Navajo/Chieftan/Mojave/T1040 · Phase: takeoff

Anomalies: conflict-ground-conflict|critical|deviation-discrepancy-procedural-published-material-policy|ground-event-encounter-vehicle

Synopsis

A PA31 pilot making a night takeoff from YIP experienced a conflict with a ground vehicle which failed to exit the runway.

Narrative

[I] called YIP Tower for clearance and taxi. Runway 5R was in use; but I requested Runway 27. (This runway was much shorter taxi time and also set me up on a perfect heading for direction of flight. Wind was calm.) Tower told me to taxi to Runway 23L Intersection G. After I read back my IFR clearance; I again asked if 27 was available since he did not acknowledge my request. I was told it was and to taxi to it.Once holding short; I called ready. A few moments later; Tower asked me if I was ready. I acknowledged; and was then cleared for takeoff. I scanned runway upon entering and saw nothing out of the ordinary. On takeoff roll; I heard Tower say something to the effect of 'Electric ##; remain clear of 27.' I figured he was telling a utility vehicle to stay clear of the runway while it was in use. I could not hear the vehicle's response because they were on a different frequency. I then heard Tower say something like; 'Electric ##; clear Runway 27 immediately!' By this time; I had started rotation; and noticed a pickup truck vehicle pulling off of the runway onto the grass.Tower never did say anything else to me about the situation once I was in the air. I was simply told to contact Departure. There was nothing else that could be done on my end to prevent such an occurrence as this from happening. The vehicle was pointed away from me; so I could not see his headlights; and the taillights of the vehicle simply blended in with all the runway lights. By the time I realized there was a conflict; the safest thing for me to do to eliminate the hazard was to continue rotation and get off the ground and away from the vehicle.Looking back on the situation; it definitely seemed that the Tower Controller was distracted or something to that effect. The fact that he missed both my initial request for Runway 27 and my call that I was ready for departure was unusual. My only other suggestion to remedy conflicts like this is to make sure that airport vehicles understand they should be listening to all transmissions that the Controller is making; even if it's not to them. At this time of night; the Tower Controller was working all frequencies. So his takeoff clearance to me was most likely transmitted on Ground frequency as well. The airport vehicle should have heard the takeoff clearance for the runway he was currently on and alerted Tower or cleared it himself.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.