37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 699734 |
Time | |
Date | 200606 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : zny.artcc |
State Reference | NY |
Altitude | msl single value : 33000 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zny.artcc |
Operator | common carrier : air carrier |
Make Model Name | A310 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zny.artcc |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : non radar |
Qualification | controller : radar controller : non radar |
ASRS Report | 699734 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | FAA ATC Human Performance |
Primary Problem | FAA |
Air Traffic Incident | Intra Facility Coordination Failure |
Situations | |
ATC Facility | computer equipment : zny.artcc |
Narrative:
Air carrier X was eastbound at FL330 in the north atlantic airspace. Another air carrier X; same call sign; was entering caribbean airspace. Atops does not recognize 2 aircraft with the same call sign. So one of the air carrier X's was removed. But there is no evidence of this happening to the controller in charge of the sector. So to make a long story short; one of the air carrier X was flying with no control. By chance it was discovered by lpaz and we took care of the situation. But it could have been bad (very bad).
Original NASA ASRS Text
Title: WHEN AN ACFT IS ENTERING ZNY OCEANIC AIRSPACE WITH A CALL SIGN IDENTICAL TO AN ACFT ALREADY IN THE AIRSPACE; THE FLT PLAN DATA IS NOT PROCESSED OR DISPLAYED BY ATOPS; THE OCEANIC AUTOMATION EQUIP.
Narrative: ACR X WAS EBOUND AT FL330 IN THE NORTH ATLANTIC AIRSPACE. ANOTHER ACR X; SAME CALL SIGN; WAS ENTERING CARIBBEAN AIRSPACE. ATOPS DOES NOT RECOGNIZE 2 ACFT WITH THE SAME CALL SIGN. SO ONE OF THE ACR X'S WAS REMOVED. BUT THERE IS NO EVIDENCE OF THIS HAPPENING TO THE CTLR IN CHARGE OF THE SECTOR. SO TO MAKE A LONG STORY SHORT; ONE OF THE ACR X WAS FLYING WITH NO CTL. BY CHANCE IT WAS DISCOVERED BY LPAZ AND WE TOOK CARE OF THE SITUATION. BUT IT COULD HAVE BEEN BAD (VERY BAD).
Data retrieved from NASA's ASRS site as of January 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.