An A320 first officer report on a destabilized approach that was experienced on an ILS to runway 22R...

Attributes
ACN	534770
Time
Date	200201
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ord.airport
Altitude	agl single value : 1000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : c90.tracon
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer only : 22r
Flight Phase	descent : approach
Route In Use	approach : instrument precision arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer pilot : multi engine
Experience	flight time last 90 days : 180 flight time total : 10000 flight time type : 1300
ASRS Report	534770
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met inflight encounter other non adherence : company policies non adherence : published procedure other anomaly
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : executed go around other
Supplementary
Problem Areas	Airspace Structure Environmental Factor Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

On downwind for an ILS runway 22R at ord, position abeam the field to the north at 4000 ft. No speed restr given. This is very unusual at ord. The unwritten rule here is you don't slow till they tell you to slow -- so we didn't. At a point approximately abeam ridge, approach said 'proceed direct ridge, maintain 3000 ft.' this is the point where the bells and whistles went off for me. We were about 7 mi from the FAF, 2000 ft high (ridge crossing altitude is 2138 ft), 250 KTS with a 30 KT tailwind. I knew it -- here comes the slam dunk. If approach control would have told us to 'expect' this, we could have slowed, got flaps and gear down, etc. Instead, we were fast and clean. We made every effort to slow down and go down while intercepting the final approach course, but when we approached 1000 ft AGL, it was obvious the approach would not be stabilized. We went around. Although ord approach should not have given us this type of approach (particularly with a ceiling), I should have not accepted it. Lesson learned.

Original NASA ASRS Text

Title: AN A320 FO RPT ON A DESTABILIZED APCH THAT WAS EXPERIENCED ON AN ILS TO RWY 22R AT ORD, IL.

Narrative: ON DOWNWIND FOR AN ILS RWY 22R AT ORD, POS ABEAM THE FIELD TO THE N AT 4000 FT. NO SPD RESTR GIVEN. THIS IS VERY UNUSUAL AT ORD. THE UNWRITTEN RULE HERE IS YOU DON'T SLOW TILL THEY TELL YOU TO SLOW -- SO WE DIDN'T. AT A POINT APPROX ABEAM RIDGE, APCH SAID 'PROCEED DIRECT RIDGE, MAINTAIN 3000 FT.' THIS IS THE POINT WHERE THE BELLS AND WHISTLES WENT OFF FOR ME. WE WERE ABOUT 7 MI FROM THE FAF, 2000 FT HIGH (RIDGE XING ALT IS 2138 FT), 250 KTS WITH A 30 KT TAILWIND. I KNEW IT -- HERE COMES THE SLAM DUNK. IF APCH CTL WOULD HAVE TOLD US TO 'EXPECT' THIS, WE COULD HAVE SLOWED, GOT FLAPS AND GEAR DOWN, ETC. INSTEAD, WE WERE FAST AND CLEAN. WE MADE EVERY EFFORT TO SLOW DOWN AND GO DOWN WHILE INTERCEPTING THE FINAL APCH COURSE, BUT WHEN WE APCHED 1000 FT AGL, IT WAS OBVIOUS THE APCH WOULD NOT BE STABILIZED. WE WENT AROUND. ALTHOUGH ORD APCH SHOULD NOT HAVE GIVEN US THIS TYPE OF APCH (PARTICULARLY WITH A CEILING), I SHOULD HAVE NOT ACCEPTED IT. LESSON LEARNED.

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.

An A320 first officer report on a destabilized approach that was experienced on an ILS to runway 22R at ord, il.