Local

August 24, 2012

Rules of the road, the airfield

Tags:
By Senior Airman Jack Sanders
99th Air Base Wing Public Affairs

Airman 1st Class Floyd Jones Jr., 57th Operational Support Squadron airfield management specialist, removes a foreign object from under a truck tire during a Foreign Object Debris check Aug. 21, 2012, at Nellis Air Force Base, Nev. FOD is potentially dangerous on airfields because it can be sucked into aircraft engines causing damage and endangering lives.

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 your 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.”

Airman 1st Class Floyd Jones Jr., 57th Operational Support Squadron airfield management specialist, performs a roll over Foreign Object Debris check Aug. 21, 2012, at Nellis Air Force Base, Nev.. FOD checks are part of training received to get a flightline drivers license.

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.”




All of this week's top headlines to your email every Friday.


 
 

 
U.S. Air Force photo by Senior Airman Thomas Spangler

Red Flag 15-3 wraps up

U.S. Air Force photo by Senior Airman Thomas Spangler A B-52 Stratofortress assigned to the 69th Bomb Squadron, Minot Air Force Base, N.D., lands during Red Flag 15-3 at Nellis AFB, Nev., July 21. A typical Red Flag exercise in...
 
 
Lockheed Martin photograph by Darin Russell

Ground testing for F-35 gun conducted at Edwards AFB

Lockheed Martin photograph by Darin Russell An F-35A Lightning II, tail number AF-2, fires a burst of rounds down range at the Edwards Gun Harmonizing Range on Edwards Air Force Base, Calif., July 17. The F-35 Joint Strike Figh...
 
 

Separated but not alone

MOUNTAIN HOME AIR FORCE BASE, Idaho — As the dawn broke out over the mountains, I woke up to the sun peeping through my window. Once I got up I went straight to the kitchen to make my family breakfast yet in the back of my mind, all I could think about was, “how am...
 

 

Mishap prevention 101

NELLIS AIR FORCE BASE, Nev. — Here is something I would like to share with my readers. This information is geared toward supervisors, but we all play a part in the mishap prevention program, and when we know better, we tend to do better. I will discuss a few things supervisors should do within their...
 
 
raptor

Raptor pilots reach 1,000 flight hours in F-22

U.S. Air Force photo by Senior Airman Joshua Kleinholz Majs. Ethan Waitte and Thomas Borrego, 422nd Test and Evaluation Squadron pilots, stand with Lt. Col. Matt Allen, 422nd TES F-22 Raptor test director, after returning from ...
 
 
U.S. Air Force photo by Airman 1st Class Christian Clausen

Creech Airmen showcase RPA at Canadian airshow

U.S. Air Force photo by Airman 1st Class Christian Clausen Senior Airman Kaitlyne LaRocque, 432nd Aircraft Maintenance Squadron MQ-1 Predator crew chief, left, and Staff Sgt. Craig Stewart, 432nd AMXS MQ-1 crew chief, prepare a...
 




0 Comments


Be the first to comment!


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>