 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A CL65 flight crew climbs out of FL280 in accordance with an acknowledged clearance to FL330, but received a TCASII RA to descend to avoid an air carrier aircraft crossing above at FL290 near vhp, in. ZID, in.
| Attributes | |
| ACN | 465562 |
| Time | |
| Date | 200003 |
| Day | Mon |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| State Reference | IN |
| Altitude | msl bound lower : 28000 msl bound upper : 28500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other other vortac |
| Flight Phase | cruise : level cruise : enroute altitude change |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other vortac |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 40 flight time total : 9000 flight time type : 40 |
| ASRS Report | 465562 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : commercial |
| Events | |
| Anomaly | altitude deviation : excursion from assigned altitude conflict : airborne critical non adherence : clearance other anomaly other |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued advisory flight crew : took evasive action |
| Consequence | faa : investigated faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 2500 vertical : 500 |
| Supplementary | |
| Problem Areas | ATC Human Performance Aircraft Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
| Situations | |
| ATC Facility | communication equipment : zid.artcc |
| Airspace Structure | class a : zid.a |
Narrative:
On mar/xa/00 I was flying from ord to roa. Our filed cruise altitude was FL370. When we were handed off to ZID we were at FL280 and had requested FL310 as our final altitude. As we approached the ind VOR, both my first officer and I thought we heard a clearance for us to climb to FL330 and expect higher soon thereafter. I then asked center to confirm this by stating 'please say again for air carrier X.' we then heard center say 'climb and maintain FL330 and expect higher soon.' I then transmitted 'climb FL330 air carrier X.' as we passed FL285, we received an RA instructing us to descend. I believe it was an air carrier aircraft that was approaching from our 3 O'clock position at FL290 that caused the conflict. They had notified ATC that they had started a climb to avoid the conflict. We stopped our climb at FL285 and descended back to FL280 as ATC asked us our altitude and instructed us to return to FL280. ATC then asked us when we received clearance to FL330. I then told ATC 'less than 1 min ago.' after reaching roa, I was told to call ZID 'quality and assurance,' which I did. Callback conversation with reporter revealed the following information: captain pulled back to say that when calling the quality assurance section of ZID he was told that the facility chief could not determine the source of the bogus clearance to FL330 but would forward the information to the local FSDO office. He has now received a notice from the local FSDO regarding this incident. He has also contacted company and the union legal office. When asked why the climb to a non requested altitude wasn't questioned, he stated that there was chop at FL280 and he felt that FL330 would provide a better ride so discounted any challenge to it. He admits to not hearing his flight name and number prior to the initial and succeeding clearance. When asked if this could have been a frequency bleed through situation, he agreed with the possibility. He stated that this has happened frequently on this aircraft and in various locations -- mostly on ZID frequencys and also near the raleigh-durham/dulles regions. He has promised to document any future occurrences of this type. The air carrier is experiencing too many altitudes excursions recently, but not necessarily in connection with a possible bleed through problem on the aircraft.
Original NASA ASRS Text
Title: A CL65 FLC CLBS OUT OF FL280 IN ACCORDANCE WITH AN ACKNOWLEDGED CLRNC TO FL330, BUT RECEIVED A TCASII RA TO DSND TO AVOID AN ACR ACFT XING ABOVE AT FL290 NEAR VHP, IN. ZID, IN.
Narrative: ON MAR/XA/00 I WAS FLYING FROM ORD TO ROA. OUR FILED CRUISE ALT WAS FL370. WHEN WE WERE HANDED OFF TO ZID WE WERE AT FL280 AND HAD REQUESTED FL310 AS OUR FINAL ALT. AS WE APCHED THE IND VOR, BOTH MY FO AND I THOUGHT WE HEARD A CLRNC FOR US TO CLB TO FL330 AND EXPECT HIGHER SOON THEREAFTER. I THEN ASKED CTR TO CONFIRM THIS BY STATING 'PLEASE SAY AGAIN FOR ACR X.' WE THEN HEARD CTR SAY 'CLB AND MAINTAIN FL330 AND EXPECT HIGHER SOON.' I THEN XMITTED 'CLB FL330 ACR X.' AS WE PASSED FL285, WE RECEIVED AN RA INSTRUCTING US TO DSND. I BELIEVE IT WAS AN ACR ACFT THAT WAS APCHING FROM OUR 3 O'CLOCK POS AT FL290 THAT CAUSED THE CONFLICT. THEY HAD NOTIFIED ATC THAT THEY HAD STARTED A CLB TO AVOID THE CONFLICT. WE STOPPED OUR CLB AT FL285 AND DSNDED BACK TO FL280 AS ATC ASKED US OUR ALT AND INSTRUCTED US TO RETURN TO FL280. ATC THEN ASKED US WHEN WE RECEIVED CLRNC TO FL330. I THEN TOLD ATC 'LESS THAN 1 MIN AGO.' AFTER REACHING ROA, I WAS TOLD TO CALL ZID 'QUALITY AND ASSURANCE,' WHICH I DID. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CAPT PULLED BACK TO SAY THAT WHEN CALLING THE QUALITY ASSURANCE SECTION OF ZID HE WAS TOLD THAT THE FACILITY CHIEF COULD NOT DETERMINE THE SOURCE OF THE BOGUS CLRNC TO FL330 BUT WOULD FORWARD THE INFO TO THE LCL FSDO OFFICE. HE HAS NOW RECEIVED A NOTICE FROM THE LCL FSDO REGARDING THIS INCIDENT. HE HAS ALSO CONTACTED COMPANY AND THE UNION LEGAL OFFICE. WHEN ASKED WHY THE CLB TO A NON REQUESTED ALT WASN'T QUESTIONED, HE STATED THAT THERE WAS CHOP AT FL280 AND HE FELT THAT FL330 WOULD PROVIDE A BETTER RIDE SO DISCOUNTED ANY CHALLENGE TO IT. HE ADMITS TO NOT HEARING HIS FLT NAME AND NUMBER PRIOR TO THE INITIAL AND SUCCEEDING CLRNC. WHEN ASKED IF THIS COULD HAVE BEEN A FREQ BLEED THROUGH SIT, HE AGREED WITH THE POSSIBILITY. HE STATED THAT THIS HAS HAPPENED FREQUENTLY ON THIS ACFT AND IN VARIOUS LOCATIONS -- MOSTLY ON ZID FREQS AND ALSO NEAR THE RALEIGH-DURHAM/DULLES REGIONS. HE HAS PROMISED TO DOCUMENT ANY FUTURE OCCURRENCES OF THIS TYPE. THE ACR IS EXPERIENCING TOO MANY ALTS EXCURSIONS RECENTLY, BUT NOT NECESSARILY IN CONNECTION WITH A POSSIBLE BLEED THROUGH PROB ON THE ACFT.
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.