37000 Feet

Browse and search NASA's Aviation Safety Reporting System

Tol TRACON controller reports of being told about a practice hung ordinance requested procedure. Controller later finds out it was not a practice; but the aircraft had actual hung ordinance and had possibly flown over populated areas.

Narrative:

My supervisor who was working as arrival data and had the shift took a call from the tower controller. The tower controller informed him that an inbound flight of military aircraft needed to do a hung ordinance procedure due to a practice bomb possibly stuck on the plane. The supervisor then informed me that the aircraft wanted to do a 'practice hung ordinance procedure.' it turns out that the supervisor misinterprited what the tower controller was saying and gave me incorrect information. I was treating it as a practice procedure and was going to work it into the rest of my pattern traffic based on what the supervisor told me. Soon after I started the flight split up and vectors to accommodate the aircrafts request I was told by the flight lead that they [had a situation] due to the hung ordinance. I asked to confirm that this was an exercise and that they wanted to do a practice procedure. At that time I was told that the hung ordinance was a practice bomb not that they wanted a practice procedure. I had to scramble to turn aircraft out of the way to accommodate the priority and to turn aircraft X away form populated areas. This would not have been needed had I been given the correct information from the supervisor. The supervisors lack of knowledge and inattention to detail contributed to making the situation much harder and unsafe than it needed to be. I am unsure how to rectify this.

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: TOL TRACON Controller reports of being told about a practice hung ordinance requested procedure. Controller later finds out it was not a practice; but the aircraft had actual hung ordinance and had possibly flown over populated areas.

Narrative: My Supervisor who was working as arrival data and had the shift took a call from the tower controller. The tower controller informed him that an inbound flight of military aircraft needed to do a hung ordinance procedure due to a practice bomb possibly stuck on the plane. The supervisor then informed me that the Aircraft wanted to do a 'practice hung ordinance procedure.' It turns out that the supervisor misinterprited what the tower controller was saying and gave me incorrect information. I was treating it as a practice procedure and was going to work it into the rest of my pattern traffic based on what the supervisor told me. Soon after I started the flight split up and vectors to accommodate the aircrafts request I was told by the flight lead that they [had a situation] due to the hung ordinance. I asked to confirm that this was an exercise and that they wanted to do a practice procedure. At that time I was told that the hung ordinance was a practice bomb not that they wanted a practice procedure. I had to scramble to turn aircraft out of the way to accommodate the priority and to turn Aircraft X away form populated areas. This would not have been needed had I been given the correct information from the supervisor. The supervisors lack of knowledge and inattention to detail contributed to making the situation much harder and unsafe than it needed to be. I am unsure how to rectify this.

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.