 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID controller is able to correct erroneous interfacility communication transfer with an aircraft at the wrong altitude, per SOP (standard operation practice).
| Attributes | |
| ACN | 530733 |
| Time | |
| Date | 200111 |
| Day | Wed |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : zid.artcc |
| State Reference | IN |
| Altitude | msl bound lower : 29000 msl bound upper : 31000 |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar controller : non radar |
| Experience | controller non radar : 3 controller radar : 11 |
| ASRS Report | 530733 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar other personnel other |
| Events | |
| Anomaly | non adherence : published procedure non adherence other other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Supplementary | |
| Problem Areas | ATC Human Performance Airspace Structure |
| Primary Problem | ATC Human Performance |
Narrative:
In attempting to call merging targets to two aircraft in my control, I realized that one aircraft was not on my frequency. The aircraft are at FL290 and FL310. The aircraft at FL310 is handed off to the adjacent sector, whom through a SOP, has control for descent to FL280 upon radio contact. The previous sector to mine inadvertently put the FL310 aircraft on the wrong frequency. When the aircraft called on to the errant frequency, the controller (low altitude) was able to discover whom had the handoff (not whose airspace the aircraft was in) and switched the aircraft to that sector. As luck would have it, the sector whom received the frequency change in error was in my area and within earshot. As I heard him giving a frequency change to the aircraft that I was expecting, I was able to contact the sector with H/O and issue the traffic to prevent them from descending the aircraft in question. Therefore no error occurred, but the potential was there.
Original NASA ASRS Text
Title: ZID CTLR IS ABLE TO CORRECT ERRONEOUS INTERFAC COM TRANSFER WITH AN ACFT AT THE WRONG ALT, PER SOP (STD OP PRACTICE).
Narrative: IN ATTEMPTING TO CALL MERGING TARGETS TO TWO ACFT IN MY CTL, I REALIZED THAT ONE ACFT WAS NOT ON MY FREQ. THE ACFT ARE AT FL290 AND FL310. THE ACFT AT FL310 IS HANDED OFF TO THE ADJACENT SECTOR, WHOM THROUGH A SOP, HAS CTL FOR DSCNT TO FL280 UPON RADIO CONTACT. THE PREVIOUS SECTOR TO MINE INADVERTENTLY PUT THE FL310 ACFT ON THE WRONG FREQ. WHEN THE ACFT CALLED ON TO THE ERRANT FREQ, THE CTLR (LOW ALT) WAS ABLE TO DISCOVER WHOM HAD THE HANDOFF (NOT WHOSE AIRSPACE THE ACFT WAS IN) AND SWITCHED THE ACFT TO THAT SECTOR. AS LUCK WOULD HAVE IT, THE SECTOR WHOM RECEIVED THE FREQ CHANGE IN ERROR WAS IN MY AREA AND WITHIN EARSHOT. AS I HEARD HIM GIVING A FREQ CHANGE TO THE ACFT THAT I WAS EXPECTING, I WAS ABLE TO CONTACT THE SECTOR WITH H/O AND ISSUE THE TFC TO PREVENT THEM FROM DSNDING THE ACFT IN QUESTION. THEREFORE NO ERROR OCCURRED, BUT THE POTENTIAL WAS THERE.
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.