This is an excerpt from a report made to the Aviation Safety Reporting System. The narrative is written by the pilot, rather than FAA or NTSB officials. To maintain anonymity, many details, such as aircraft model or airport, are often scrubbed from the reports.
I completed a run-up at the departure end penalty box and observed an airport vehicle depart the same place.
As I was preparing to taxi, a jet called my aircraft identifying by location to request my intentions. I stated “run up complete but he can start a back taxi.” I started the taxi to the active runway. He declined in favor of my departure.
I called “taxi and departure Runway X, VFR to the east.”
I rolled on to the runway displaced threshold while checking for traffic on final. I observed the jet had not moved but he called and requested if anyone else was inbound to land, to no response.
I checked my Mooney M-20 was secured, and after rolling some of the displaced threshold, checked instruments and passengers, and applied full power.
After reaching rotation speed, I observed the airport vehicle cross the runway in front of me. It appeared he was playing chicken. I considered rejecting the takeoff but could not be certain the power changes and braking would help avoid the collision.
Thankfully the vehicle cleared the runway and I was off the ground moments later.
I think safety can be improved by having ground vehicles at uncontrolled airports stating their intentions. A simple call of “crossing the active runway” would have improved safety as I could check and delay my takeoff.
I called on CTAF during departure that the ground vehicles crossing was “not good” and another voice agreed. I met the driver later and he was the voice that replied.
As pilot in command, I will improve by maintaining situational awareness of aircraft and NORDO ground vehicles. It was a busy time with other traffic and that is a good reminder to double check your aircraft and intended path.
Primary Problem: Human Factors
ACN: 1805857
Always use “Takeoff” when you takeoff. Flight attendants use “depart” or “departing” to sound fancy to the passengers (think Elaine in the “Airplane!” movie), but it has no meaning with respect to and aircraft taking off from a runway. Unfortunately it has worked its way into the vernacular. The only time you might depart a runway is when you loose control and end up in the grass before actually “taking off”.
The Mooney’s actions were correct as the voice agreeing to the “not good ” statement of the Mooney was the ground vehicle meaning he had a radio and failed to announce that he was “crossing the runway. While the Mooney would have the same issue had a “NORDO “deer crossed the runway the fact that the ground vehicle had a radio and his not using it created the situation. Hats off to the Mooney for making the right calls.
The driver of the ground vehicle was probably confused by the Mooney pilot’s radio call. Calling for taxi and departure in a single radio call is not a good practice. In fact, the Mooney pilot after making such a call is psychologically committed to rushing onto the runway without checking that final and the runway are clear, since he already announced his departure.
I agree. I think a pilot should say “Winchester Traffic, Skyhawk 1234F, taking off Runway 14, Winchester Traffic,” for example, at Winchester.
Airport name, information, airport name. And the word “TAKEOFF,” not ‘depart.” And “VFR to the west,” is not needed, either.
Someone can correct me if I’m wrong, but during my initial flight training my instructor told me “take off” should not be used to announce one’s departure from an airport? I never use it. My call at our un-towered airport is:
“city traffic, 1 2 3 delta, departing runway 35, leaving the pattern to the west, city traffic.”
I think that’s very good phraseology. The example in the AIM is “Strawn traffic, Queen Air Seven One Five Five Bravo
departing runway two six. Departing the pattern to the
(direction), climbing to (altitude) Strawn.” (para 4-1-9-g-6-(b)).