37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 192218 |
Time | |
Date | 199110 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : cyn |
State Reference | NJ |
Altitude | msl bound lower : 8000 msl bound upper : 9000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Transport, Low Wing, 2 Recip Eng |
Flight Phase | cruise other |
Route In Use | enroute airway : v16 |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : atp pilot : instrument pilot : cfi |
Experience | flight time last 90 days : 120 flight time total : 3670 flight time type : 240 |
ASRS Report | 192218 |
Person 2 | |
Affiliation | Other |
Function | observation : passenger |
Qualification | pilot : private |
Events | |
Anomaly | conflict : airborne less severe other anomaly other |
Independent Detector | atc equipment other atc equipment : unspecified |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
I was plting the owner's small transport on an IFR flight from islip, long island (isp) to lynchburg, va (lyh) on V-16. At 8000 ft we had entered clouds and the passenger were beginning to become uneasy with the turbulence and rain. Around cyn VOR I requested 10000 as a new altitude, believing that this would get us above the cloud tops. Mcguire approach could not approve higher on our assigned route, so I advised the controller that I would accept an alternate routing if he could clear us for higher. A few moments later he called back with an amended clearance which I read back, no altitude change. I was then handed off to ZDC, from whom I again requested higher. The controller said that there would be a delay for higher, but when I advised him that one of the passenger was becoming queasy he was good enough to clear us to 9000. Within a couple hundred ft of level off, an urgent voice directed us to 'descend immediately to 8000'. Asking no questions, I began an immediate descent. The controller said that our assigned altitude was 8000. I replied that, negative, we had been cleared up to 9000. He claimed that the clearance to 9000 had been revoked after it was issued. I did not hear the 9000 ft altitude amended and I certainly did not acknowledge this new altitude assignment. The aircraft's owner (a rated pilot) was seated next to me and was monitoring the flight and occasionally helping out with the radio communications. He also only heard the clearance to 9000 and not any subsequent amendment. About a min later, through a break in the clouds, I was able to see an airliner cross our flight path from left to right at 9000. We were subsequently cleared to 10000 where we broke out on top and continued to the destination without further incident. I don't believe that there is anything I could have done to prevent this incident. I was attentive to the radios and had another pilot also monitoring communications. It seems unlikely that we would both miss a call. The controller should have demanded an acknowledgement to his revocation of a clearance I had previously accepted, I feel, in any case.
Original NASA ASRS Text
Title: LTSS BTWN GA-SMT AND AN ACR ACFT AT 9000 FT SW OF CYN.
Narrative: I WAS PLTING THE OWNER'S SMT ON AN IFR FLT FROM ISLIP, LONG ISLAND (ISP) TO LYNCHBURG, VA (LYH) ON V-16. AT 8000 FT WE HAD ENTERED CLOUDS AND THE PAX WERE BEGINNING TO BECOME UNEASY WITH THE TURB AND RAIN. AROUND CYN VOR I REQUESTED 10000 AS A NEW ALT, BELIEVING THAT THIS WOULD GET US ABOVE THE CLOUD TOPS. MCGUIRE APCH COULD NOT APPROVE HIGHER ON OUR ASSIGNED RTE, SO I ADVISED THE CTLR THAT I WOULD ACCEPT AN ALTERNATE RTING IF HE COULD CLR US FOR HIGHER. A FEW MOMENTS LATER HE CALLED BACK WITH AN AMENDED CLRNC WHICH I READ BACK, NO ALT CHANGE. I WAS THEN HANDED OFF TO ZDC, FROM WHOM I AGAIN REQUESTED HIGHER. THE CTLR SAID THAT THERE WOULD BE A DELAY FOR HIGHER, BUT WHEN I ADVISED HIM THAT ONE OF THE PAX WAS BECOMING QUEASY HE WAS GOOD ENOUGH TO CLR US TO 9000. WITHIN A COUPLE HUNDRED FT OF LEVEL OFF, AN URGENT VOICE DIRECTED US TO 'DSND IMMEDIATELY TO 8000'. ASKING NO QUESTIONS, I BEGAN AN IMMEDIATE DSCNT. THE CTLR SAID THAT OUR ASSIGNED ALT WAS 8000. I REPLIED THAT, NEGATIVE, WE HAD BEEN CLRED UP TO 9000. HE CLAIMED THAT THE CLRNC TO 9000 HAD BEEN REVOKED AFTER IT WAS ISSUED. I DID NOT HEAR THE 9000 FT ALT AMENDED AND I CERTAINLY DID NOT ACKNOWLEDGE THIS NEW ALT ASSIGNMENT. THE ACFT'S OWNER (A RATED PLT) WAS SEATED NEXT TO ME AND WAS MONITORING THE FLT AND OCCASIONALLY HELPING OUT WITH THE RADIO COMS. HE ALSO ONLY HEARD THE CLRNC TO 9000 AND NOT ANY SUBSEQUENT AMENDMENT. ABOUT A MIN LATER, THROUGH A BREAK IN THE CLOUDS, I WAS ABLE TO SEE AN AIRLINER CROSS OUR FLT PATH FROM L TO R AT 9000. WE WERE SUBSEQUENTLY CLRED TO 10000 WHERE WE BROKE OUT ON TOP AND CONTINUED TO THE DEST WITHOUT FURTHER INCIDENT. I DON'T BELIEVE THAT THERE IS ANYTHING I COULD HAVE DONE TO PREVENT THIS INCIDENT. I WAS ATTENTIVE TO THE RADIOS AND HAD ANOTHER PLT ALSO MONITORING COMS. IT SEEMS UNLIKELY THAT WE WOULD BOTH MISS A CALL. THE CTLR SHOULD HAVE DEMANDED AN ACKNOWLEDGEMENT TO HIS REVOCATION OF A CLRNC I HAD PREVIOUSLY ACCEPTED, I FEEL, IN ANY CASE.
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.