 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew in muha airspace are instructed to contact mmid center. Flight crew is concerned when mmid center issues a descent clearance while they are still in the muha airspace.
| Attributes | |
| ACN | 418230 |
| Time | |
| Date | 199810 |
| Day | Mon |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : cun |
| State Reference | FO |
| Altitude | msl bound lower : 22000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : mmid artcc : muha |
| Operator | common carrier : air carrier |
| Make Model Name | B737-400 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | cruise other descent other |
| Route In Use | enroute : other oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | other pilot : atp |
| Experience | flight time last 90 days : 180 flight time total : 8900 flight time type : 6000 |
| ASRS Report | 418230 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 300 flight time total : 18000 flight time type : 10000 |
| ASRS Report | 418229 |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | other |
Narrative:
We were flying in havana airspace at FL330. We contacted merida center 10 mins prior to fdr, as required. Merida cleared us to FL220. While still in havana airspace, the FMC began a descent to meet a programmed restr for landing in cun. Just after beginning descent, havana cleared us to contact merida. No conflict occurred and neither havana nor merida questioned us. We probably should not have descended until merida airspace boundary or got specific permission from havana. However, it seems like bad policy for one center to issue altitude clrncs while in another center's airspace. The merida clearance probably should have been 'after passing fdr boundary instrument, cleared to FL220.' or, they should coordination with havana and advise when issuing the clearance. Or as ZMA usually says, 'with havana's approval, cleared to XXXX.'
Original NASA ASRS Text
Title: B737 FLC IN MUHA AIRSPACE ARE INSTRUCTED TO CONTACT MMID CTR. FLC IS CONCERNED WHEN MMID CTR ISSUES A DSCNT CLRNC WHILE THEY ARE STILL IN THE MUHA AIRSPACE.
Narrative: WE WERE FLYING IN HAVANA AIRSPACE AT FL330. WE CONTACTED MERIDA CTR 10 MINS PRIOR TO FDR, AS REQUIRED. MERIDA CLRED US TO FL220. WHILE STILL IN HAVANA AIRSPACE, THE FMC BEGAN A DSCNT TO MEET A PROGRAMMED RESTR FOR LNDG IN CUN. JUST AFTER BEGINNING DSCNT, HAVANA CLRED US TO CONTACT MERIDA. NO CONFLICT OCCURRED AND NEITHER HAVANA NOR MERIDA QUESTIONED US. WE PROBABLY SHOULD NOT HAVE DSNDED UNTIL MERIDA AIRSPACE BOUNDARY OR GOT SPECIFIC PERMISSION FROM HAVANA. HOWEVER, IT SEEMS LIKE BAD POLICY FOR ONE CTR TO ISSUE ALT CLRNCS WHILE IN ANOTHER CTR'S AIRSPACE. THE MERIDA CLRNC PROBABLY SHOULD HAVE BEEN 'AFTER PASSING FDR BOUNDARY INST, CLRED TO FL220.' OR, THEY SHOULD COORD WITH HAVANA AND ADVISE WHEN ISSUING THE CLRNC. OR AS ZMA USUALLY SAYS, 'WITH HAVANA'S APPROVAL, CLRED TO XXXX.'
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.