A319 captain looses situational awareness while attempting landing at stl, complicated by WX, fatigue and lack of timely response by stl approach controller resulting in a 360 degree on final to reestablish a stable approach.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	612453
Time
Date	200403
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : stl.airport
State Reference	MO
Aircraft 1
Controlling Facilities	artcc : zkc.artcc tracon : t75.tracon tower : stl.tower
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	cruise : level descent : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time total : 14500 flight time type : 4500
ASRS Report	612453
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : less severe inflight encounter : weather non adherence : published procedure other anomaly
Independent Detector	other flight crewa
Resolutory Action	controller : separated traffic controller : issued new clearance flight crew : became reoriented flight crew : exited adverse environment
Supplementary
Problem Areas	Flight Crew Human Performance Weather Environmental Factor ATC Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Approximately 150 mi west of stl, a broken line of WX had formed. ZKC approved deviations and suggested a route through an area of only light rain on the radar. I agreed to the routing. The first officer was getting the ATIS when ATC cleared us from FL370 to 15000 ft. 100 mi west of stl, we were told to stop at FL270 for traffic. The turbulence light chop/turbulence, with light rain, but the static was high. The #1 radio was impossible to hear. I tried calling center, but did not hear any replies. 75 mi from stl, center was able to get through with a descent to 15000 ft. We were handed off to stl approach and given a vector for an 8 mi final for runway 12R, visual approach. By this time, I had started to slow and configure. We had a 45 KT tailwind. I realized at this time we were about 3000 ft high on the profile. Everything happened at once. 1 mi from the localizer, ATC gave a turn to intercept, near the OM. We informed ATC we were high and needed delay vectors. The controller came back with, 'I have traffic on both downwinds. What do you want to do?

Original NASA ASRS Text

Title: A319 CAPT LOOSES SITUATIONAL AWARENESS WHILE ATTEMPTING LNDG AT STL, COMPLICATED BY WX, FATIGUE AND LACK OF TIMELY RESPONSE BY STL APCH CTLR RESULTING IN A 360 DEG ON FINAL TO REESTABLISH A STABLE APCH.

Narrative: APPROX 150 MI W OF STL, A BROKEN LINE OF WX HAD FORMED. ZKC APPROVED DEVS AND SUGGESTED A RTE THROUGH AN AREA OF ONLY LIGHT RAIN ON THE RADAR. I AGREED TO THE ROUTING. THE FO WAS GETTING THE ATIS WHEN ATC CLRED US FROM FL370 TO 15000 FT. 100 MI W OF STL, WE WERE TOLD TO STOP AT FL270 FOR TFC. THE TURB LIGHT CHOP/TURB, WITH LIGHT RAIN, BUT THE STATIC WAS HIGH. THE #1 RADIO WAS IMPOSSIBLE TO HEAR. I TRIED CALLING CTR, BUT DID NOT HEAR ANY REPLIES. 75 MI FROM STL, CTR WAS ABLE TO GET THROUGH WITH A DSCNT TO 15000 FT. WE WERE HANDED OFF TO STL APCH AND GIVEN A VECTOR FOR AN 8 MI FINAL FOR RWY 12R, VISUAL APCH. BY THIS TIME, I HAD STARTED TO SLOW AND CONFIGURE. WE HAD A 45 KT TAILWIND. I REALIZED AT THIS TIME WE WERE ABOUT 3000 FT HIGH ON THE PROFILE. EVERYTHING HAPPENED AT ONCE. 1 MI FROM THE LOC, ATC GAVE A TURN TO INTERCEPT, NEAR THE OM. WE INFORMED ATC WE WERE HIGH AND NEEDED DELAY VECTORS. THE CTLR CAME BACK WITH, 'I HAVE TFC ON BOTH DOWNWINDS. WHAT DO YOU WANT TO DO?

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.