37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 805586 |
Time | |
Date | 200809 |
Place | |
Locale Reference | airport : cha.airport |
State Reference | TN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : cha.tower |
Operator | common carrier : air carrier |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : local |
Experience | controller radar : 19 |
ASRS Report | 805586 |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Miss Distance | horizontal : 18000 vertical : 500 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
I was working local control at cha combined with the controller in charge position. Trainee working ground and clearance (he/she certified on those position). This was the first day of having our main runway closed for construction. We were using our crossing runway for arrs and departures. At some point; one of the commuter flts received permission from airport management to use the long runway (the one that was closed). The departure had a flow control slot time so they were holding on the ramp waiting on the time. Meanwhile; I had heard ground control coordinating with the airport management personnel concerning the departure. I was told that everything was worked out and that they were approved for departure on the long (closed) runway. In other words; the runway would be opened briefly for that one departure. Also; at that time; I had aircraft call for departure and a helicopter depart. I had to radar identify the helicopter; complete a flight progress strip for their flight; forward the strip to the TRACON; and start an automated handoff. As soon as the flow control slot time arrived; I confirmed with the ground controller that everything was ok for the departure on the temporarily opened runway. At that time; I issued back-taxi instructions and also issued the takeoff clearance. Just after the aircraft departed I realized that I had not coordination a release with the departure controller and that there was traffic for the departure. I immediately coordination with the departure controller and turned the departure away from the traffic crossing his departure path. I do not believe that there was less than standard separation between the aircraft. Also; I applied visual separation between the 2 aircraft. There was no further problems. I do believe that there were many distrs that came into play. 1) a major taxiway resurfacing project underway. 2) using our short crossing runway as the active. 3) the long normally active runway being closed. 4) working local combined with the controller in charge position. Other factors that could have caused me to make the mistake: 1) having an inexperienced trainee working ground. A more experienced controller may have caught my mistake (and would have been working the controller in charge position). 2) the departure was using our primary runway that would normally have automatic releases. (We had automatic released on the other runway at the time.)
Original NASA ASRS Text
Title: CHA LCL CTLR RELEASED DEP WITHOUT APPROPRIATE COORD WITH DEP CTLR RESULTING IN NEAR LOSS OF SEPARATION AT 2500 FT.
Narrative: I WAS WORKING LCL CTL AT CHA COMBINED WITH THE CIC POS. TRAINEE WORKING GND AND CLRNC (HE/SHE CERTIFIED ON THOSE POS). THIS WAS THE FIRST DAY OF HAVING OUR MAIN RWY CLOSED FOR CONSTRUCTION. WE WERE USING OUR XING RWY FOR ARRS AND DEPS. AT SOME POINT; ONE OF THE COMMUTER FLTS RECEIVED PERMISSION FROM ARPT MGMNT TO USE THE LONG RWY (THE ONE THAT WAS CLOSED). THE DEP HAD A FLOW CTL SLOT TIME SO THEY WERE HOLDING ON THE RAMP WAITING ON THE TIME. MEANWHILE; I HAD HEARD GND CTL COORDINATING WITH THE ARPT MGMNT PERSONNEL CONCERNING THE DEP. I WAS TOLD THAT EVERYTHING WAS WORKED OUT AND THAT THEY WERE APPROVED FOR DEP ON THE LONG (CLOSED) RWY. IN OTHER WORDS; THE RWY WOULD BE OPENED BRIEFLY FOR THAT ONE DEP. ALSO; AT THAT TIME; I HAD ACFT CALL FOR DEP AND A HELI DEPART. I HAD TO RADAR IDENT THE HELI; COMPLETE A FLT PROGRESS STRIP FOR THEIR FLT; FORWARD THE STRIP TO THE TRACON; AND START AN AUTOMATED HDOF. AS SOON AS THE FLOW CTL SLOT TIME ARRIVED; I CONFIRMED WITH THE GND CTLR THAT EVERYTHING WAS OK FOR THE DEP ON THE TEMPORARILY OPENED RWY. AT THAT TIME; I ISSUED BACK-TAXI INSTRUCTIONS AND ALSO ISSUED THE TKOF CLRNC. JUST AFTER THE ACFT DEPARTED I REALIZED THAT I HAD NOT COORD A RELEASE WITH THE DEP CTLR AND THAT THERE WAS TFC FOR THE DEP. I IMMEDIATELY COORD WITH THE DEP CTLR AND TURNED THE DEP AWAY FROM THE TFC XING HIS DEP PATH. I DO NOT BELIEVE THAT THERE WAS LESS THAN STANDARD SEPARATION BTWN THE ACFT. ALSO; I APPLIED VISUAL SEPARATION BTWN THE 2 ACFT. THERE WAS NO FURTHER PROBS. I DO BELIEVE THAT THERE WERE MANY DISTRS THAT CAME INTO PLAY. 1) A MAJOR TXWY RESURFACING PROJECT UNDERWAY. 2) USING OUR SHORT XING RWY AS THE ACTIVE. 3) THE LONG NORMALLY ACTIVE RWY BEING CLOSED. 4) WORKING LCL COMBINED WITH THE CIC POS. OTHER FACTORS THAT COULD HAVE CAUSED ME TO MAKE THE MISTAKE: 1) HAVING AN INEXPERIENCED TRAINEE WORKING GND. A MORE EXPERIENCED CTLR MAY HAVE CAUGHT MY MISTAKE (AND WOULD HAVE BEEN WORKING THE CIC POS). 2) THE DEP WAS USING OUR PRIMARY RWY THAT WOULD NORMALLY HAVE AUTOMATIC RELEASES. (WE HAD AUTOMATIC RELEASED ON THE OTHER RWY AT THE TIME.)
Data retrieved from NASA's ASRS site as of May 2009 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.