37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 411225 |
Time | |
Date | 199808 |
Day | Sun |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | atc facility : einn |
State Reference | FO |
Altitude | msl bound lower : 31000 msl bound upper : 34000 |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Controlling Facilities | artcc : eggx tower : sfo |
Operator | common carrier : air carrier |
Make Model Name | B767 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : atlantic enroute other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel |
Qualification | other other : other |
ASRS Report | 411225 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | other anomaly other other anomaly other |
Independent Detector | other flight crewa other other : unspecified |
Resolutory Action | none taken : anomaly accepted other |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
I received a call from the cockpit of flight XXX, captain XXX. At about XX30Z, the flight was coming up on 20 mi west in the north atlantic track system. The flight had been released with TCASII system deferral. The MEL route was requiring the dispatcher to plan the flight to avoid rvsm airspace which had been done by filing the oceanic portion at FL310 beneath the FL330 floor of rvsm. Captain XXX called to advise me of his situation. Just south of ireland and still in radar control prior to oceanic entry he requested and received clearance to FL340 in order to top some convective WX in his path. Inadvertently this seems to have boxed the flight into that altitude. Having cleared the threatening WX, shanwick was unable to approve the flight back down to FL310. The flight made continued requests for FL310 even advising the shanwick controller that their TCASII was inoperative which restricted them from rvsm. The controller rptedly replied that TCASII was not required for rvsm airspace. Captain XXX felt that his options were either to proceed 30 mi north or to stay at FL340 in VMC on the presently cleared routing. I could offer no further suggestions and concurred. I advised the captain of the following points. First, that we had complied with the MEL by planning the flight beneath rvsm airspace. I have been aware of the deferral from my turnover briefing log. Next, within radar control, higher altitude was requested -- in the best judgement of the captain, the most prudent course of action for WX avoidance. Finally, I called the captain's attention to B767 operations manual. Pink bulletin referencing rvsm. It delineates equipment which must be operational to enter rvsm airspace. TCASII is not mentioned. He said he was already on the page. Hence, the sequence of events. Flight was properly planned. WX avoidance caused unusual event. Unable to comply with original plan, account ATC constraints. Still in compliance with operating manual. We agreed that going 1 degree north of the track and descending was tantamount to declaring an emergency, which we did not intend. Our best course was to remain at FL340 as cleared by ATC, which was also in VMC.
Original NASA ASRS Text
Title: B767 ACR DISPATCHER WAS CONCERNED ABOUT ENTERING ATLANTIC RVSM AIRSPACE WITH A TCASII MEL'ED INOP.
Narrative: I RECEIVED A CALL FROM THE COCKPIT OF FLT XXX, CAPT XXX. AT ABOUT XX30Z, THE FLT WAS COMING UP ON 20 MI W IN THE NORTH ATLANTIC TRACK SYS. THE FLT HAD BEEN RELEASED WITH TCASII SYS DEFERRAL. THE MEL RTE WAS REQUIRING THE DISPATCHER TO PLAN THE FLT TO AVOID RVSM AIRSPACE WHICH HAD BEEN DONE BY FILING THE OCEANIC PORTION AT FL310 BENEATH THE FL330 FLOOR OF RVSM. CAPT XXX CALLED TO ADVISE ME OF HIS SIT. JUST S OF IRELAND AND STILL IN RADAR CTL PRIOR TO OCEANIC ENTRY HE REQUESTED AND RECEIVED CLRNC TO FL340 IN ORDER TO TOP SOME CONVECTIVE WX IN HIS PATH. INADVERTENTLY THIS SEEMS TO HAVE BOXED THE FLT INTO THAT ALT. HAVING CLRED THE THREATENING WX, SHANWICK WAS UNABLE TO APPROVE THE FLT BACK DOWN TO FL310. THE FLT MADE CONTINUED REQUESTS FOR FL310 EVEN ADVISING THE SHANWICK CTLR THAT THEIR TCASII WAS INOP WHICH RESTRICTED THEM FROM RVSM. THE CTLR RPTEDLY REPLIED THAT TCASII WAS NOT REQUIRED FOR RVSM AIRSPACE. CAPT XXX FELT THAT HIS OPTIONS WERE EITHER TO PROCEED 30 MI N OR TO STAY AT FL340 IN VMC ON THE PRESENTLY CLRED ROUTING. I COULD OFFER NO FURTHER SUGGESTIONS AND CONCURRED. I ADVISED THE CAPT OF THE FOLLOWING POINTS. FIRST, THAT WE HAD COMPLIED WITH THE MEL BY PLANNING THE FLT BENEATH RVSM AIRSPACE. I HAVE BEEN AWARE OF THE DEFERRAL FROM MY TURNOVER BRIEFING LOG. NEXT, WITHIN RADAR CTL, HIGHER ALT WAS REQUESTED -- IN THE BEST JUDGEMENT OF THE CAPT, THE MOST PRUDENT COURSE OF ACTION FOR WX AVOIDANCE. FINALLY, I CALLED THE CAPT'S ATTN TO B767 OPS MANUAL. PINK BULLETIN REFING RVSM. IT DELINEATES EQUIP WHICH MUST BE OPERATIONAL TO ENTER RVSM AIRSPACE. TCASII IS NOT MENTIONED. HE SAID HE WAS ALREADY ON THE PAGE. HENCE, THE SEQUENCE OF EVENTS. FLT WAS PROPERLY PLANNED. WX AVOIDANCE CAUSED UNUSUAL EVENT. UNABLE TO COMPLY WITH ORIGINAL PLAN, ACCOUNT ATC CONSTRAINTS. STILL IN COMPLIANCE WITH OPERATING MANUAL. WE AGREED THAT GOING 1 DEG N OF THE TRACK AND DSNDING WAS TANTAMOUNT TO DECLARING AN EMER, WHICH WE DID NOT INTEND. OUR BEST COURSE WAS TO REMAIN AT FL340 AS CLRED BY ATC, WHICH WAS ALSO IN VMC.
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.