37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 540506 |
Time | |
Date | 200203 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : nuq.airport |
State Reference | CA |
Altitude | msl bound lower : 7000 msl bound upper : 7200 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : o90.tracon tower : nuq.tower |
Operator | other |
Make Model Name | Citation V |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure sid : southland 9 |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : o90.tracon |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | climbout : intermediate altitude |
Person 1 | |
Affiliation | government : military |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 50 flight time total : 3000 flight time type : 600 |
ASRS Report | 540506 |
Person 2 | |
Affiliation | government : military |
Function | flight crew : first officer |
Events | |
Anomaly | altitude deviation : crossing restriction not met altitude deviation : overshoot conflict : airborne less severe non adherence : clearance non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : radar aircraft equipment : tcas other controllera |
Resolutory Action | controller : issued new clearance controller : issued alert |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 12000 vertical : 2000 |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft commander called for clearance 1/2 hour before departure sitting in the right seat. Departure was as filed: southland 9 departure, avenal transition, climb and maintain 15000 ft, expect FL290 10 mins after departure, contact departure 121.3, squawk XXXX. Read back 'cleared as filed, climb maintain 15000 ft, expect FL290 10 mins after departure, 121.3, squawk XXXX, over.' taxi for takeoff, takeoff runway 32L. Took off, climbed up, switched departure when cleared by tower, checked in with departure, called 'aircraft X turning right heading 090 degrees, climbing through 1400 ft for 15000 ft.' believe I got a roger. A few moments later, approach called traffic, our TCASII came up yellow with an alert. Both pilots visually acquired the traffic and called climbing above heading 090 degrees no factor. Climb profile was continued. After a few more moments, controller asked for our departure. We repeated cleared as filed climb maintain 15000 ft expect FL290 10 mins after departure. Controller asked us to level at 7000 ft. We had passed 7200 ft and descended back to 7000 ft. Controller gave us a vector and pointed out altitudes on the plate that we rogered at that time, but reiterated that we had been cleared up to 15000 ft. Controller asked that we call ATC upon landing. Remainder of flight unremarkable. Called ATC upon arrival at destination after complete. Told him we were a military crew. Explained the altitude confusion to ATC and he seemed to understand that there was confusion and the departure call to ATC. ATC contends that when cleared via a departure, departure altitudes are to be maintained even when you are cleared to a higher altitude -- confusing at best. Crew contends that when given a climb and maintain altitude that this information is last clearance given and is expected to be complied with. Posed this scenario to other pilots with thousands of hours of experience. They, too, said that in this situation the last altitude clearance given was to 15000 ft, and that is what they would climb to. If lost communication had been encountered, we would have climbed to 15000 ft, punched the clock, and then after 10 mins gone up to FL290 on the filed and cleared route of flight as our expected clearance dictated. This confusion could have been avoided and the chain broken in 2 ways: 1) when clearance was given by clearance delivery, if aircrew is expected to follow the departure altitudes the clearance could read 'aircraft X cleared via the departure, then as filed, expect FL290 10 mins after departure....' this alerts the air crew that they are following the SID, expecting FL290 10 mins down the road. 2) when the initial departure call was made, 'aircraft X checking in, passing 1400 ft for 15000 ft, turning right to 090 degrees,' if the controller had come back 'aircraft X, negative, level off at 4000 ft,' the link in the chain of events would have been broken. I know now to question all altitudes and confirm cleared to altitude after SID completion. My hope is that this event will serve as an example to help others. I will brief this scenario in our next pilot training session so that others may learn from a confusing situation. The irony of this event starting at the NASA facility is not lost on me. Thank you for your time and attention.
Original NASA ASRS Text
Title: AN MTR CREW, DEPARTING KNUQ, MISINTERPED THEIR CLRNC, STARTING A CLB TO 15000 FT UNRESTR, INSTEAD OF ADHERING TO THE SID RESTRS.
Narrative: ACFT COMMANDER CALLED FOR CLRNC 1/2 HR BEFORE DEP SITTING IN THE R SEAT. DEP WAS AS FILED: SOUTHLAND 9 DEP, AVENAL TRANSITION, CLB AND MAINTAIN 15000 FT, EXPECT FL290 10 MINS AFTER DEP, CONTACT DEP 121.3, SQUAWK XXXX. READ BACK 'CLRED AS FILED, CLB MAINTAIN 15000 FT, EXPECT FL290 10 MINS AFTER DEP, 121.3, SQUAWK XXXX, OVER.' TAXI FOR TKOF, TKOF RWY 32L. TOOK OFF, CLBED UP, SWITCHED DEP WHEN CLRED BY TWR, CHKED IN WITH DEP, CALLED 'ACFT X TURNING R HDG 090 DEGS, CLBING THROUGH 1400 FT FOR 15000 FT.' BELIEVE I GOT A ROGER. A FEW MOMENTS LATER, APCH CALLED TFC, OUR TCASII CAME UP YELLOW WITH AN ALERT. BOTH PLTS VISUALLY ACQUIRED THE TFC AND CALLED CLBING ABOVE HDG 090 DEGS NO FACTOR. CLB PROFILE WAS CONTINUED. AFTER A FEW MORE MOMENTS, CTLR ASKED FOR OUR DEP. WE REPEATED CLRED AS FILED CLB MAINTAIN 15000 FT EXPECT FL290 10 MINS AFTER DEP. CTLR ASKED US TO LEVEL AT 7000 FT. WE HAD PASSED 7200 FT AND DSNDED BACK TO 7000 FT. CTLR GAVE US A VECTOR AND POINTED OUT ALTS ON THE PLATE THAT WE ROGERED AT THAT TIME, BUT REITERATED THAT WE HAD BEEN CLRED UP TO 15000 FT. CTLR ASKED THAT WE CALL ATC UPON LNDG. REMAINDER OF FLT UNREMARKABLE. CALLED ATC UPON ARR AT DEST AFTER COMPLETE. TOLD HIM WE WERE A MIL CREW. EXPLAINED THE ALT CONFUSION TO ATC AND HE SEEMED TO UNDERSTAND THAT THERE WAS CONFUSION AND THE DEP CALL TO ATC. ATC CONTENDS THAT WHEN CLRED VIA A DEP, DEP ALTS ARE TO BE MAINTAINED EVEN WHEN YOU ARE CLRED TO A HIGHER ALT -- CONFUSING AT BEST. CREW CONTENDS THAT WHEN GIVEN A CLB AND MAINTAIN ALT THAT THIS INFO IS LAST CLRNC GIVEN AND IS EXPECTED TO BE COMPLIED WITH. POSED THIS SCENARIO TO OTHER PLTS WITH THOUSANDS OF HRS OF EXPERIENCE. THEY, TOO, SAID THAT IN THIS SIT THE LAST ALT CLRNC GIVEN WAS TO 15000 FT, AND THAT IS WHAT THEY WOULD CLB TO. IF LOST COM HAD BEEN ENCOUNTERED, WE WOULD HAVE CLBED TO 15000 FT, PUNCHED THE CLOCK, AND THEN AFTER 10 MINS GONE UP TO FL290 ON THE FILED AND CLRED RTE OF FLT AS OUR EXPECTED CLRNC DICTATED. THIS CONFUSION COULD HAVE BEEN AVOIDED AND THE CHAIN BROKEN IN 2 WAYS: 1) WHEN CLRNC WAS GIVEN BY CLRNC DELIVERY, IF AIRCREW IS EXPECTED TO FOLLOW THE DEP ALTS THE CLRNC COULD READ 'ACFT X CLRED VIA THE DEP, THEN AS FILED, EXPECT FL290 10 MINS AFTER DEP....' THIS ALERTS THE AIR CREW THAT THEY ARE FOLLOWING THE SID, EXPECTING FL290 10 MINS DOWN THE ROAD. 2) WHEN THE INITIAL DEP CALL WAS MADE, 'ACFT X CHKING IN, PASSING 1400 FT FOR 15000 FT, TURNING R TO 090 DEGS,' IF THE CTLR HAD COME BACK 'ACFT X, NEGATIVE, LEVEL OFF AT 4000 FT,' THE LINK IN THE CHAIN OF EVENTS WOULD HAVE BEEN BROKEN. I KNOW NOW TO QUESTION ALL ALTS AND CONFIRM CLRED TO ALT AFTER SID COMPLETION. MY HOPE IS THAT THIS EVENT WILL SERVE AS AN EXAMPLE TO HELP OTHERS. I WILL BRIEF THIS SCENARIO IN OUR NEXT PLT TRAINING SESSION SO THAT OTHERS MAY LEARN FROM A CONFUSING SIT. THE IRONY OF THIS EVENT STARTING AT THE NASA FACILITY IS NOT LOST ON ME. THANK YOU FOR YOUR TIME AND ATTN.
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.