 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of medium large transport on arrival route encounters an annoyed controller due to lack of descent clearance prior to handoff. In the ensuing clearance they are given a wrong fix and query the controller who changes the clearance to the correct fix. The next clearance is complicated with several segments. Captain is off frequency and first officer mixes up the altitude and distance numbers missing the crossing restr.
| Attributes | |
| ACN | 385170 |
| Time | |
| Date | 199711 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : lin |
| State Reference | CA |
| Altitude | msl bound lower : 21000 msl bound upper : 25000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent other |
| Route In Use | arrival other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 200 flight time total : 12000 flight time type : 200 |
| ASRS Report | 385170 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | altitude deviation : crossing restriction not met non adherence : clearance other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Wraps 5 arrival from ont-smf, I was getting ATIS on #2 radio, not monitoring #1 radio. First officer was flying aircraft and switched over to next controller. That controller was upset because we weren't given the normal crossing restr of 24000 ft at turlo intersection. He then cleared us to cross 25 mi south of manteca at 21000 ft or below, cross linden at 16000 ft or below, and descend to 11000 ft. It took the first officer a few seconds to realize this was a bogus clearance (we were not going to manteca). He then told the controller who then read back cross 25 DME south of linden 21000 ft or below, cross linden 16000 ft or below and cross twane at 11000 ft. The first officer read back clearance. I then switched over to #1 radio, asked first officer what our clearance was. He told me but wasn't quite sure about the 11000 ft, so he called and verified it. The first officer must have thought at or below 25000 ft at 21 DME, because the controller called back and asked why we weren't below our altitude restr. The controller was rightfully upset. The first officer realized mistake. A lot was going on. The first officer was expecting a certain clearance, received a wrong clearance, received a rather complicated clearance read to him quickly. Because of poor coordination between the 2 controllers, I was off the radio at the time so couldn't help my first officer, he interpolated the numbers in his mind, I did not monitor him as much as I should have. I was also busy switching vors and trying to figure out where we were (first officer on LNAV). Bottom line, we were wrong and I need to monitor first officer more closely.
Original NASA ASRS Text
Title: FLC OF MLG ON ARR RTE ENCOUNTERS AN ANNOYED CTLR DUE TO LACK OF DSCNT CLRNC PRIOR TO HDOF. IN THE ENSUING CLRNC THEY ARE GIVEN A WRONG FIX AND QUERY THE CTLR WHO CHANGES THE CLRNC TO THE CORRECT FIX. THE NEXT CLRNC IS COMPLICATED WITH SEVERAL SEGMENTS. CAPT IS OFF FREQ AND FO MIXES UP THE ALT AND DISTANCE NUMBERS MISSING THE XING RESTR.
Narrative: WRAPS 5 ARR FROM ONT-SMF, I WAS GETTING ATIS ON #2 RADIO, NOT MONITORING #1 RADIO. FO WAS FLYING ACFT AND SWITCHED OVER TO NEXT CTLR. THAT CTLR WAS UPSET BECAUSE WE WEREN'T GIVEN THE NORMAL XING RESTR OF 24000 FT AT TURLO INTXN. HE THEN CLRED US TO CROSS 25 MI S OF MANTECA AT 21000 FT OR BELOW, CROSS LINDEN AT 16000 FT OR BELOW, AND DSND TO 11000 FT. IT TOOK THE FO A FEW SECONDS TO REALIZE THIS WAS A BOGUS CLRNC (WE WERE NOT GOING TO MANTECA). HE THEN TOLD THE CTLR WHO THEN READ BACK CROSS 25 DME S OF LINDEN 21000 FT OR BELOW, CROSS LINDEN 16000 FT OR BELOW AND CROSS TWANE AT 11000 FT. THE FO READ BACK CLRNC. I THEN SWITCHED OVER TO #1 RADIO, ASKED FO WHAT OUR CLRNC WAS. HE TOLD ME BUT WASN'T QUITE SURE ABOUT THE 11000 FT, SO HE CALLED AND VERIFIED IT. THE FO MUST HAVE THOUGHT AT OR BELOW 25000 FT AT 21 DME, BECAUSE THE CTLR CALLED BACK AND ASKED WHY WE WEREN'T BELOW OUR ALT RESTR. THE CTLR WAS RIGHTFULLY UPSET. THE FO REALIZED MISTAKE. A LOT WAS GOING ON. THE FO WAS EXPECTING A CERTAIN CLRNC, RECEIVED A WRONG CLRNC, RECEIVED A RATHER COMPLICATED CLRNC READ TO HIM QUICKLY. BECAUSE OF POOR COORD BTWN THE 2 CTLRS, I WAS OFF THE RADIO AT THE TIME SO COULDN'T HELP MY FO, HE INTERPOLATED THE NUMBERS IN HIS MIND, I DID NOT MONITOR HIM AS MUCH AS I SHOULD HAVE. I WAS ALSO BUSY SWITCHING VORS AND TRYING TO FIGURE OUT WHERE WE WERE (FO ON LNAV). BOTTOM LINE, WE WERE WRONG AND I NEED TO MONITOR FO MORE CLOSELY.
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.