 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 departing non radar area had copied clearance as filed maintain FL330. Set FL310 in the alerter in error. Controller contacted flight when level at FL310 questioning clearance. Again cleared to FL330.
| Attributes | |
| ACN | 345140 |
| Time | |
| Date | 199608 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : sya |
| State Reference | AK |
| Altitude | msl bound lower : 31000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zan |
| Operator | common carrier : air carrier |
| Make Model Name | B737-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : intermediate altitude cruise other ground : preflight |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : instrument pilot : cfi pilot : atp pilot : commercial |
| Experience | flight time last 90 days : 280 flight time total : 15000 flight time type : 8000 |
| ASRS Report | 345140 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : atp pilot : instrument |
| Experience | flight time last 90 days : 75 flight time total : 10000 flight time type : 2000 |
| ASRS Report | 345294 |
| Events | |
| Anomaly | altitude deviation : undershoot non adherence : clearance non adherence : far non adherence other |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance flight crew : became reoriented other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Departure was from uncontrolled airport in a non radar environment. First officer obtained clearance directly from ATC while I was securing the cabin area. Ran the before start checklist. I asked first officer if we had a clearance, said yes, cleared as filed to FL310. I verified altitude alerter. After level for about 10 mins, ATC asked our altitude, we replied FL310. About 10 mins later, ATC asked our cleared to altitude, again replied FL310 and requested FL330. Cleared to FL330. Looked at flight plan where first officer had written clearance. He had written down FL330 -- mostly likely what we were originally cleared to. Could not recall initial calls to ATC after takeoff. I do not know if we reported climbing to FL310 -- that was set in alerter or FL330. Also do not recall if we reported level FL310. By the time we are level on this leg we are usually out of radio and radar contact. The fix: 1) do not deviate from company policy that requires captain to be listening when first officer gets clearance. 2) verify what is written as 'clearance received' with what is set in altitude alerter. 3) verify what altitude flight plan is filed for versus clearance received. 4) any time cruise altitude is wrong for direction of flight reverify everything. Supplemental information from acn 345294: we were clear as filed climb and maintain FL330. Captain was in the back of airplane securing cargo door for departure. I set the flight altitude alerter while I was talking on the radio and inadvertently set FL480 and then wound it down to FL310. Leveled at FL310. I thought the captain had got an intermediate climb to altitude of FL310.
Original NASA ASRS Text
Title: B737 DEPARTING NON RADAR AREA HAD COPIED CLRNC AS FILED MAINTAIN FL330. SET FL310 IN THE ALERTER IN ERROR. CTLR CONTACTED FLT WHEN LEVEL AT FL310 QUESTIONING CLRNC. AGAIN CLRED TO FL330.
Narrative: DEP WAS FROM UNCTLED ARPT IN A NON RADAR ENVIRONMENT. FO OBTAINED CLRNC DIRECTLY FROM ATC WHILE I WAS SECURING THE CABIN AREA. RAN THE BEFORE START CHKLIST. I ASKED FO IF WE HAD A CLRNC, SAID YES, CLRED AS FILED TO FL310. I VERIFIED ALT ALERTER. AFTER LEVEL FOR ABOUT 10 MINS, ATC ASKED OUR ALT, WE REPLIED FL310. ABOUT 10 MINS LATER, ATC ASKED OUR CLRED TO ALT, AGAIN REPLIED FL310 AND REQUESTED FL330. CLRED TO FL330. LOOKED AT FLT PLAN WHERE FO HAD WRITTEN CLRNC. HE HAD WRITTEN DOWN FL330 -- MOSTLY LIKELY WHAT WE WERE ORIGINALLY CLRED TO. COULD NOT RECALL INITIAL CALLS TO ATC AFTER TKOF. I DO NOT KNOW IF WE RPTED CLBING TO FL310 -- THAT WAS SET IN ALERTER OR FL330. ALSO DO NOT RECALL IF WE RPTED LEVEL FL310. BY THE TIME WE ARE LEVEL ON THIS LEG WE ARE USUALLY OUT OF RADIO AND RADAR CONTACT. THE FIX: 1) DO NOT DEVIATE FROM COMPANY POLICY THAT REQUIRES CAPT TO BE LISTENING WHEN FO GETS CLRNC. 2) VERIFY WHAT IS WRITTEN AS 'CLRNC RECEIVED' WITH WHAT IS SET IN ALT ALERTER. 3) VERIFY WHAT ALT FLT PLAN IS FILED FOR VERSUS CLRNC RECEIVED. 4) ANY TIME CRUISE ALT IS WRONG FOR DIRECTION OF FLT REVERIFY EVERYTHING. SUPPLEMENTAL INFO FROM ACN 345294: WE WERE CLR AS FILED CLB AND MAINTAIN FL330. CAPT WAS IN THE BACK OF AIRPLANE SECURING CARGO DOOR FOR DEP. I SET THE FLT ALT ALERTER WHILE I WAS TALKING ON THE RADIO AND INADVERTENTLY SET FL480 AND THEN WOUND IT DOWN TO FL310. LEVELED AT FL310. I THOUGHT THE CAPT HAD GOT AN INTERMEDIATE CLB TO ALT OF FL310.
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.