 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Improper ARTCC intrafac coordination. Air carrier X climb through occupied altitude, had less than standard separation from air carrier Y. System error.
| Attributes | |
| ACN | 302060 |
| Time | |
| Date | 199504 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : ape |
| State Reference | OH |
| Altitude | msl bound lower : 16000 msl bound upper : 16000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : phl |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise other |
| Route In Use | enroute : direct enroute airway : zid |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 3 |
| ASRS Report | 302060 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller non radar : 3 controller radar : 2 |
| ASRS Report | 302061 |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | atc equipment other atc equipment : unspecified |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 9000 vertical : 300 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Narrative:
I was working cmh radar and had handed off and switched air carrier Y. The data block was dropped after he left my airspace. The ltl controller flashed air carrier X climbing to 15000 ft and I took the handoff. Just after the handoff, air carrier Z was flashed climbing to FL190 (out of 14000 ft). The ltl controller advised air carrier X requested 17000 ft and was my control reference 'the air carrier.' when air carrier X was clear of air carrier Z I issued the air carrier X climbing to 17000 ft. After aedp, I learned that air carrier X was the traffic he intended. The limited data block on air carrier Y was covered by the data block on air carrier X. I thought the air carrier Y was long gone and got no pvd from ltl. The error happened 17 mi on ltl's side of the sector boundary. Same company was coming from another sector, but I thought ltl had a pointout on him because of the deviations. As it turned out, air carrier Y was the only same company on his scope, hence 'your control reference the air carrier.' air carrier Z was the only same company air carrier on my scope. Supplemental information from acn 302061: air carrier X level at 15000 ft requested 17000 ft. Traffic was called (air carrier Y at 16000 ft). Air carrier X was told higher was available clearing traffic. I spoke to the receiving controller and stated that air carrier X wanted higher and was his control clearing air carrier Y. The other controller thought the reference was to a different same company aircraft. Proper coordination would probably have prevented this.
Original NASA ASRS Text
Title: IMPROPER ARTCC INTRAFAC COORD. ACR X CLB THROUGH OCCUPIED ALT, HAD LTSS FROM ACR Y. SYS ERROR.
Narrative: I WAS WORKING CMH RADAR AND HAD HANDED OFF AND SWITCHED ACR Y. THE DATA BLOCK WAS DROPPED AFTER HE LEFT MY AIRSPACE. THE LTL CTLR FLASHED ACR X CLBING TO 15000 FT AND I TOOK THE HDOF. JUST AFTER THE HDOF, ACR Z WAS FLASHED CLBING TO FL190 (OUT OF 14000 FT). THE LTL CTLR ADVISED ACR X REQUESTED 17000 FT AND WAS MY CTL REF 'THE ACR.' WHEN ACR X WAS CLR OF ACR Z I ISSUED THE ACR X CLBING TO 17000 FT. AFTER AEDP, I LEARNED THAT ACR X WAS THE TFC HE INTENDED. THE LIMITED DATA BLOCK ON ACR Y WAS COVERED BY THE DATA BLOCK ON ACR X. I THOUGHT THE ACR Y WAS LONG GONE AND GOT NO PVD FROM LTL. THE ERROR HAPPENED 17 MI ON LTL'S SIDE OF THE SECTOR BOUNDARY. SAME COMPANY WAS COMING FROM ANOTHER SECTOR, BUT I THOUGHT LTL HAD A POINTOUT ON HIM BECAUSE OF THE DEVS. AS IT TURNED OUT, ACR Y WAS THE ONLY SAME COMPANY ON HIS SCOPE, HENCE 'YOUR CTL REF THE ACR.' ACR Z WAS THE ONLY SAME COMPANY ACR ON MY SCOPE. SUPPLEMENTAL INFO FROM ACN 302061: ACR X LEVEL AT 15000 FT REQUESTED 17000 FT. TFC WAS CALLED (ACR Y AT 16000 FT). ACR X WAS TOLD HIGHER WAS AVAILABLE CLRING TFC. I SPOKE TO THE RECEIVING CTLR AND STATED THAT ACR X WANTED HIGHER AND WAS HIS CTL CLRING ACR Y. THE OTHER CTLR THOUGHT THE REF WAS TO A DIFFERENT SAME COMPANY ACFT. PROPER COORD WOULD PROBABLY HAVE PREVENTED THIS.
Data retrieved from NASA's ASRS site as of July 2007 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.