 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Operating in multiple foreign airspace, a controller from one country received flight crew position report and had them change frequency to the next country controller. However, the controller failed to pass on to the next controller the flight crew's position report. Consequently, the aircraft crossed the fir boundary and the controllers from the next country had no information on the flight crew aircraft.
| Attributes | |
| ACN | 335110 |
| Time | |
| Date | 199605 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : tci |
| State Reference | FO |
| Altitude | msl bound lower : 33000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | DC-10 30F |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | cruise other |
| Route In Use | enroute airway : gccc |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : flight engineer pilot : commercial |
| Experience | flight time last 90 days : 200 flight time total : 20000 flight time type : 200 |
| ASRS Report | 335110 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : atp |
| Experience | flight time last 90 days : 150 flight time total : 4400 flight time type : 200 |
| ASRS Report | 335270 |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Inter Facility Coordination Failure |
Narrative:
We were operating as air carrier X flight yy, a DC10-30F freighter. While in level cruise on a trip from egss to sbkp, we made a standard non-radar position report over 'konba' intersection to casablanca control. Casablanca control acknowledged our report. Aprox 10 mins later, casablanca gave us a frequency change to canaries control. We then gave canaries control the same position report we had just made to casablanca. The new controller acknowledged our report and gave us a discrete code to squawk. After several mins the controller informed us that we were in radar contact. Shortly thereafter, we were advised to contact another controller (possibly the supervisor) who wanted to talk to us about a problem. This new controller asked us why we had flown 150 mi into canaries airspace without checking in ('konba' intersection is the canaries IFR boundary). He further stated that 'you were lucky we had you in radar contact.' we responded that we had made all normal frequency changes and reports. I also asked the first controller if he had received all of our position reports and estimates. He acknowledged that he had, and didn't seem to think that there was any problem. I believe what happened is the following. Over 'konba' casablanca failed to hand us off to canaries control after we made our position report. We did not query him about this. Once he realized his mistake he gave us the frequency change. By that time, we had flown a number of mi into the canaries airspace. Unlike some fir boundaries around the world, the en route charts for this area do not instruct us to contact canaries control prior to crossing their boundary. Our suggestion is to have this information printed on the en route chart. I never believed we were in danger at any time, but the potential is always lurking there.
Original NASA ASRS Text
Title: OPERATING IN MULTIPLE FOREIGN AIRSPACE, A CTLR FROM ONE COUNTRY RECEIVED FLC POS RPT AND HAD THEM CHANGE FREQ TO THE NEXT COUNTRY CTLR. HOWEVER, THE CTLR FAILED TO PASS ON TO THE NEXT CTLR THE FLC'S POS RPT. CONSEQUENTLY, THE ACFT CROSSED THE FIR BOUNDARY AND THE CTLRS FROM THE NEXT COUNTRY HAD NO INFO ON THE FLC ACFT.
Narrative: WE WERE OPERATING AS ACR X FLT YY, A DC10-30F FREIGHTER. WHILE IN LEVEL CRUISE ON A TRIP FROM EGSS TO SBKP, WE MADE A STANDARD NON-RADAR POS RPT OVER 'KONBA' INTXN TO CASABLANCA CTL. CASABLANCA CTL ACKNOWLEDGED OUR REPORT. APROX 10 MINS LATER, CASABLANCA GAVE US A FREQ CHANGE TO CANARIES CTL. WE THEN GAVE CANARIES CTL THE SAME POS RPT WE HAD JUST MADE TO CASABLANCA. THE NEW CTLR ACKNOWLEDGED OUR RPT AND GAVE US A DISCRETE CODE TO SQUAWK. AFTER SEVERAL MINS THE CTLR INFORMED US THAT WE WERE IN RADAR CONTACT. SHORTLY THEREAFTER, WE WERE ADVISED TO CONTACT ANOTHER CTLR (POSSIBLY THE SUPVR) WHO WANTED TO TALK TO US ABOUT A PROB. THIS NEW CTLR ASKED US WHY WE HAD FLOWN 150 MI INTO CANARIES AIRSPACE WITHOUT CHKING IN ('KONBA' INTXN IS THE CANARIES IFR BOUNDARY). HE FURTHER STATED THAT 'YOU WERE LUCKY WE HAD YOU IN RADAR CONTACT.' WE RESPONDED THAT WE HAD MADE ALL NORMAL FREQ CHANGES AND RPTS. I ALSO ASKED THE FIRST CTLR IF HE HAD RECEIVED ALL OF OUR POS RPTS AND ESTIMATES. HE ACKNOWLEDGED THAT HE HAD, AND DIDN'T SEEM TO THINK THAT THERE WAS ANY PROB. I BELIEVE WHAT HAPPENED IS THE FOLLOWING. OVER 'KONBA' CASABLANCA FAILED TO HAND US OFF TO CANARIES CTL AFTER WE MADE OUR POS RPT. WE DID NOT QUERY HIM ABOUT THIS. ONCE HE REALIZED HIS MISTAKE HE GAVE US THE FREQ CHANGE. BY THAT TIME, WE HAD FLOWN A NUMBER OF MI INTO THE CANARIES AIRSPACE. UNLIKE SOME FIR BOUNDARIES AROUND THE WORLD, THE ENRTE CHARTS FOR THIS AREA DO NOT INSTRUCT US TO CONTACT CANARIES CTL PRIOR TO XING THEIR BOUNDARY. OUR SUGGESTION IS TO HAVE THIS INFO PRINTED ON THE ENRTE CHART. I NEVER BELIEVED WE WERE IN DANGER AT ANY TIME, BUT THE POTENTIAL IS ALWAYS LURKING 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.