HomeMediaArticle Display

Rules of the road, the airfield

NELLIS AIR FORCE BASE, Nev. -- Driving onto the Airfield at an Air Force base can be a daunting process for any Airman.

There are so many things that need to be remembered to be safe. Drivers must ensure they conduct roll over foreign object debris checks at all FOD points, stay back 200 feet from taxiing aircraft, ensure they're not crossing hold line and performing many other checks procedures.

"Flightline driving isn't any different from regular driving," said Airman 1st Class Floyd Jones Jr., 57th Operation Support Squadron airfield management operations coordinator. "You are required to have your state and GOV driver's license and restricted area badge before you're able to get a flightline drivers license. Then, you have to go through training and understand the procedures, such as performing FOD checks or calling up to the tower before crossing the runways. Those are things you need to know before getting your flightline drivers license, and while you're on the flightline."

The tasks may be daunting, but ensuring they're done right can potentially save millions in Air Force assets and save lives.

"It's very essential," Jones said. "Safety procedures and precautions are important, because it only takes that one little pebble getting sucked into an Aircraft to have serious issues."

Airmen preparing for flightline driving must take computer based training, have a current flightline access badge and Air Force form 483 flightline driving competency card. Drivers on the airfield must be aware of their airfields specific requirements also.

"For airfield driving the final say is Airfield Management," Jones said. "Security Forces is out there for security reasons, for the aircraft and if Airfield Management needs assistance, but at the end of the day it ultimately comes down to Airfield Management flightline driving policies. If drivers are on the Airfield without a 483, then they're will be escorted off. It doesn't matter who it is, if you don't have a 483, you're not qualified to be driving on Airfield and driving. You will be escorted off the flightline."

Construction on the airfield may provide extra concerns for the flightline drivers, aircraft and Airfield Management Airmen. Flightline drivers are responsible for informing Airfield Management for violations they see on the flightline.

"If you see FOD caused by construction, on the flightline, that's something we need to know about, so we can respond," Jones said. "If construction is causing FOD to get onto the runway, apron or the taxi ways and if it gets into the Aircraft it could be potentially dangerous."

Every person on the flightline is responsible for what happens on it, Jones said.

"We must have the integrity to do things and do them right," Jones said. "Airmen out there doing FOD checks must conduct roll over FOD checks. I see a lot of people out there doing FOD checks, but they're not doing roll over FOD checks. CMA violations are also a concerns. It's something that can be controlled through training, integrity and situational awareness. If we all do our part we can continue to provide a safe airfield environment."

Original content found here.
USAF Comments Policy
If you wish to comment, use the text box below. AF reserves the right to modify this policy at any time.

This is a moderated forum. That means all comments will be reviewed before posting. In addition, we expect that participants will treat each other, as well as our agency and our employees, with respect. We will not post comments that contain abusive or vulgar language, spam, hate speech, personal attacks, violate EEO policy, are offensive to other or similar content. We will not post comments that are spam, are clearly "off topic", promote services or products, infringe copyright protected material, or contain any links that don't contribute to the discussion. Comments that make unsupported accusations will also not be posted. The AF and the AF alone will make a determination as to which comments will be posted. Any references to commercial entities, products, services, or other non-governmental organizations or individuals that remain on the site are provided solely for the information of individuals using this page. These references are not intended to reflect the opinion of the AF, DoD, the United States, or its officers or employees concerning the significance, priority, or importance to be given the referenced entity, product, service, or organization. Such references are not an official or personal endorsement of any product, person, or service, and may not be quoted or reproduced for the purpose of stating or implying AF endorsement or approval of any product, person, or service.

Any comments that report criminal activity including: suicidal behaviour or sexual assault will be reported to appropriate authorities including OSI. This forum is not:

  • This forum is not to be used to report criminal activity. If you have information for law enforcement, please contact OSI or your local police agency.
  • Do not submit unsolicited proposals, or other business ideas or inquiries to this forum. This site is not to be used for contracting or commercial business.
  • This forum may not be used for the submission of any claim, demand, informal or formal complaint, or any other form of legal and/or administrative notice or process, or for the exhaustion of any legal and/or administrative remedy.

AF does not guarantee or warrant that any information posted by individuals on this forum is correct, and disclaims any liability for any loss or damage resulting from reliance on any such information. AF may not be able to verify, does not warrant or guarantee, and assumes no liability for anything posted on this website by any other person. AF does not endorse, support or otherwise promote any private or commercial entity or the information, products or services contained on those websites that may be reached through links on our website.

Members of the media are asked to send questions to the public affairs through their normal channels and to refrain from submitting questions here as comments. Reporter questions will not be posted. We recognize that the Web is a 24/7 medium, and your comments are welcome at any time. However, given the need to manage federal resources, moderating and posting of comments will occur during regular business hours Monday through Friday. Comments submitted after hours or on weekends will be read and posted as early as possible; in most cases, this means the next business day.

For the benefit of robust discussion, we ask that comments remain "on-topic." This means that comments will be posted only as it relates to the topic that is being discussed within the blog post. The views expressed on the site by non-federal commentators do not necessarily reflect the official views of the AF or the Federal Government.

To protect your own privacy and the privacy of others, please do not include personally identifiable information, such as name, Social Security number, DoD ID number, OSI Case number, phone numbers or email addresses in the body of your comment. If you do voluntarily include personally identifiable information in your comment, such as your name, that comment may or may not be posted on the page. If your comment is posted, your name will not be redacted or removed. In no circumstances will comments be posted that contain Social Security numbers, DoD ID numbers, OSI case numbers, addresses, email address or phone numbers. The default for the posting of comments is "anonymous", but if you opt not to, any information, including your login name, may be displayed on our site.

Thank you for taking the time to read this comment policy. We encourage your participation in our discussion and look forward to an active exchange of ideas.