<< >> NASA ASRS Report 451760, October 1999

A B737-300 first officer, PNF, noted that the captain would not make their crossing restr. ATC gave them a new heading and altitude.

Attributes
ACN	451760
Time
Date	199910
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	intersection : fuzzy
State Reference	NV
Altitude	msl single value : 19000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : l30.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival star : fuzzy 4
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : cfi pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 240 flight time total : 8300 flight time type : 1800
ASRS Report	451760
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Flight from rno-las on fuzzy four arrival, cleared to cross fuzzy intersection at, I believe, 16000 ft or 17000 ft, by ZLA. I left radio frequency #1 to go to #2 radio to receive ATIS and call company for gate information. When I returned I saw that the captain was not going to make the crossing restr, so I told him he was above the profile descent. He realized he was high, so talking to las vegas approach control, approximately 10 mi from fuzzy intersection, the captain told them he was going to be high for the crossing restr and asked for any relief from the restr. Approach control said no problem and told him to turn to an assigned heading and descent and maintain a lower altitude, because we would be flying towards the airport and then making right traffic for runway 1R in las vegas. Again, las vegas approach control said there was not going to be a problem with not meeting the crossing restr, and had assigned a heading off the arrival and a lower altitude to descend to prior to fuzzy intersection.

Related reports:

• B737-300 first officer set up the FMC; but failed to set the...
• A B737-300 flight crew failed to make a descent crossing res...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A B737-300 FO, PNF, NOTED THAT THE CAPT WOULD NOT MAKE THEIR XING RESTR. ATC GAVE THEM A NEW HEADING AND ALT.

Narrative: FLT FROM RNO-LAS ON FUZZY FOUR ARR, CLRED TO CROSS FUZZY INTXN AT, I BELIEVE, 16000 FT OR 17000 FT, BY ZLA. I LEFT RADIO FREQ #1 TO GO TO #2 RADIO TO RECEIVE ATIS AND CALL COMPANY FOR GATE INFO. WHEN I RETURNED I SAW THAT THE CAPT WAS NOT GOING TO MAKE THE XING RESTR, SO I TOLD HIM HE WAS ABOVE THE PROFILE DSCNT. HE REALIZED HE WAS HIGH, SO TALKING TO LAS VEGAS APCH CTL, APPROX 10 MI FROM FUZZY INTXN, THE CAPT TOLD THEM HE WAS GOING TO BE HIGH FOR THE XING RESTR AND ASKED FOR ANY RELIEF FROM THE RESTR. APCH CTL SAID NO PROB AND TOLD HIM TO TURN TO AN ASSIGNED HEADING AND DSCNT AND MAINTAIN A LOWER ALT, BECAUSE WE WOULD BE FLYING TOWARDS THE ARPT AND THEN MAKING R TFC FOR RWY 1R IN LAS VEGAS. AGAIN, LAS VEGAS APCH CTL SAID THERE WAS NOT GOING TO BE A PROB WITH NOT MEETING THE XING RESTR, AND HAD ASSIGNED A HEADING OFF THE ARR AND A LOWER ALT TO DSND TO PRIOR TO FUZZY INTXN.

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.