37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1381252 |
Time | |
Date | 201607 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | DAL.Airport |
State Reference | TX |
Aircraft 1 | |
Make Model Name | Boeing Company Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Other / Unknown |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (mon) 9 Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Incursion Taxiway Ground Incursion Runway |
Narrative:
This was a vip movement for [government aircraft]. The controllers working did not receive a briefing of any kind about the operation. Management was on several telcons prior; and relayed zero information to the front line controllers. That being said; there was not a clear line of authority. Who calls the ramp freeze? The airport operations? Secret service rep in the tower?since we had no briefing; that means there was a movement area violation by the [government] motorcade (between 20-50 vehicles). They came out on to taxiway a without the ground controllers permission or prior knowledge at the south end of FBO ramp; to the north end of FBO ramp. No prior coordination/notice had been given to the ground controller.second; there was a runway incursion. The two vehicles followed the aircraft for his taxi from the FBO ramp from the departure end of runway 13 left until the exit at runway 18 and on to taxiway alpha. Aircraft called for taxi. Those vehicles continued their movement area violations when aircraft departed by returning to the FBO ramp via taxiway alpha.third; since there was no briefing to the controllers; the 7110.65 says to give [certain government] aircraft 9000 AGL on departure as initial altitude to the max extent possible. Our sids go to 8000 MSL; about 7500 AGL. Myself and the ground controller brought this up; and the flm (front line manager) in charge snapped at me in front of everyone in the tower cab; which included the atm (air traffic manager) and secret service rep; yelling that was not going to happen.fourth; there was also a discrepancy on how to read a new full route clearance to the pilot; and the atm stated that it could not be done in the tower cab; though the pilot was requesting it on frequency. The pilot eventually got the full route clearance.fifth; aircraft was delayed by between one to two minutes at the runway hold line by the local west controller and flm for an undetermined reason. Traffic was not a factor.brief the controllers on the operation. Our atm has a documented history of not providing briefings and also providing untimely briefings. We have had background checks; many have held secret or better security clearances. The operation details the day of are fouo (for official use only). We are allowed to know that information.
Original NASA ASRS Text
Title: Dallas Love Controller reported not being briefed for a VIP movement and what resulted afterward.
Narrative: This was a VIP movement for [government aircraft]. The controllers working did not receive a briefing of any kind about the operation. Management was on several TELCONs prior; and relayed ZERO information to the front line controllers. That being said; there was not a clear line of authority. Who calls the ramp freeze? The Airport Operations? Secret Service rep in the tower?Since we had no briefing; that means there was a movement area violation by the [government] motorcade (between 20-50 vehicles). They came out on to Taxiway A without the ground controllers permission or prior knowledge at the south end of FBO ramp; to the North end of FBO Ramp. No prior coordination/notice had been given to the ground controller.Second; there was a runway incursion. The two vehicles followed the aircraft for his taxi from the FBO Ramp from the departure end of runway 13 Left until the exit at runway 18 and on to Taxiway Alpha. Aircraft called for taxi. Those vehicles continued their movement area violations when aircraft departed by returning to the FBO ramp via taxiway Alpha.Third; since there was no briefing to the controllers; the 7110.65 says to give [certain government] aircraft 9000 AGL on departure as initial altitude to the max extent possible. Our SIDS go to 8000 MSL; about 7500 AGL. Myself and the ground controller brought this up; and the FLM (Front Line Manager) in charge snapped at me in front of everyone in the tower cab; which included the ATM (Air Traffic Manager) and Secret Service rep; yelling that was not going to happen.Fourth; there was also a discrepancy on how to read a new full route clearance to the pilot; and the ATM stated that it could not be done in the tower cab; though the pilot was requesting it on frequency. The pilot eventually got the full route clearance.Fifth; aircraft was delayed by between one to two minutes at the runway hold line by the Local West Controller and FLM for an undetermined reason. Traffic was not a factor.Brief the Controllers on the operation. Our ATM has a documented history of not providing briefings and also providing untimely briefings. We have had background checks; many have held Secret or better security clearances. The operation details the day of are FOUO (For Official Use Only). We are allowed to know that information.
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.