Altitude deviation. Crossing restr not met. ATC assigned 310 KTS for descent and, though reporter first officer crosschecked their profile progress, they still ended up 800 ft high at the crossing restr fix. Reporter notes that using a managed descent profile without reference to speed can get one into such a situation.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	342620
Time
Date	199607
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : rwf
State Reference	MN
Altitude	msl bound lower : 11000 msl bound upper : 11800
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zmp
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	arrival other arrival star : star
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 130 flight time total : 3900 flight time type : 260
ASRS Report	342620
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were on the redwood falls arrival STAR. I selected a managed descent profile, after commencing descent we were assigned 310 KIAS. I crosschecked at 18000 ft and we were on profile. We completed the descent and approach checks and were assigned a crossing altitude of 11000 ft. I selected 11000 ft in the altitude indicator window and continued descent. I rechked and we were still on profile. Just prior to seane intersection, out of 13000 ft, center handed us off to approach control. Our first contact with approach control was at 11800 ft at seane intersection. Both the captain and I realized that we were 800 ft high and waited to be level at 11000 ft before making the radio call. There was no response from center or approach in reference to our altitude. We knew we were slightly high at the fix and I wanted to fill out a report due to the situation that one can get into when using a managed descent profile without reference to the speed. Closer attention must be paid to the descent profile.

Original NASA ASRS Text

Title: ALTDEV. XING RESTR NOT MET. ATC ASSIGNED 310 KTS FOR DSCNT AND, THOUGH RPTR FO XCHKED THEIR PROFILE PROGRESS, THEY STILL ENDED UP 800 FT HIGH AT THE XING RESTR FIX. RPTR NOTES THAT USING A MANAGED DSCNT PROFILE WITHOUT REF TO SPD CAN GET ONE INTO SUCH A SIT.

Narrative: WE WERE ON THE REDWOOD FALLS ARR STAR. I SELECTED A MANAGED DSCNT PROFILE, AFTER COMMENCING DSCNT WE WERE ASSIGNED 310 KIAS. I XCHKED AT 18000 FT AND WE WERE ON PROFILE. WE COMPLETED THE DSCNT AND APCH CHKS AND WERE ASSIGNED A XING ALT OF 11000 FT. I SELECTED 11000 FT IN THE ALT INDICATOR WINDOW AND CONTINUED DSCNT. I RECHKED AND WE WERE STILL ON PROFILE. JUST PRIOR TO SEANE INTXN, OUT OF 13000 FT, CTR HANDED US OFF TO APCH CTL. OUR FIRST CONTACT WITH APCH CTL WAS AT 11800 FT AT SEANE INTXN. BOTH THE CAPT AND I REALIZED THAT WE WERE 800 FT HIGH AND WAITED TO BE LEVEL AT 11000 FT BEFORE MAKING THE RADIO CALL. THERE WAS NO RESPONSE FROM CTR OR APCH IN REF TO OUR ALT. WE KNEW WE WERE SLIGHTLY HIGH AT THE FIX AND I WANTED TO FILL OUT A RPT DUE TO THE SIT THAT ONE CAN GET INTO WHEN USING A MANAGED DSCNT PROFILE WITHOUT REF TO THE SPD. CLOSER ATTN MUST BE PAID TO THE DSCNT PROFILE.

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.