An air carrier crew reports the mdw local controller cleared a B737 for takeoff while they were on final forcing them to go around and getting a TCAS TA near the ground.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	758507
Time
Date	200710
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mdw.airport
State Reference	IL
Environment
Flight Conditions	VMC
Aircraft 1
Controlling Facilities	tower : mdw.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	descent : approach landing : go around
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : mdw.tower
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
ASRS Report	758507
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	758508
Events
Anomaly	conflict : airborne critical non adherence : published procedure non adherence : far
Independent Detector	other flight crewa
Resolutory Action	flight crew : executed go around flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

On approach to runway 22L in mdw; we were cleared to land. Shortly thereafter; a B737 was cleared for takeoff on same runway. While the B737 was on takeoff roll; tower instructed us to go around. On the go around; we were initially instructed runway heading; then a left turn; then a right turn; then runway heading. The right turn was intended for aircraft Y; but the controller used our call sign instead. Fortunately; these instructions were all issued before we had a chance to act on any of them. While climbing through 2000 ft; we spotted aircraft Y below us in a right turn. We were then issued vectors for left traffic back to runway 22L. Experience told both the captain and myself that we were too close behind an aircraft taking off. We should have initiated a go around on our own sooner. Also; aircraft Y could have noticed how close we were before taking the runway or they could have refused the takeoff clearance; forcing us to go around but not having to worry about 2 aircraft over the runway at once.

Original NASA ASRS Text

Title: AN ACR CREW REPORTS THE MDW LOCAL CTLR CLEARED A B737 FOR TKOF WHILE THEY WERE ON FINAL FORCING THEM TO GAR AND GETTING A TCAS TA NEAR THE GROUND.

Narrative: ON APCH TO RWY 22L IN MDW; WE WERE CLRED TO LAND. SHORTLY THEREAFTER; A B737 WAS CLRED FOR TKOF ON SAME RWY. WHILE THE B737 WAS ON TKOF ROLL; TWR INSTRUCTED US TO GO AROUND. ON THE GAR; WE WERE INITIALLY INSTRUCTED RWY HDG; THEN A L TURN; THEN A R TURN; THEN RWY HDG. THE R TURN WAS INTENDED FOR ACFT Y; BUT THE CTLR USED OUR CALL SIGN INSTEAD. FORTUNATELY; THESE INSTRUCTIONS WERE ALL ISSUED BEFORE WE HAD A CHANCE TO ACT ON ANY OF THEM. WHILE CLBING THROUGH 2000 FT; WE SPOTTED ACFT Y BELOW US IN A R TURN. WE WERE THEN ISSUED VECTORS FOR L TFC BACK TO RWY 22L. EXPERIENCE TOLD BOTH THE CAPT AND MYSELF THAT WE WERE TOO CLOSE BEHIND AN ACFT TAKING OFF. WE SHOULD HAVE INITIATED A GAR ON OUR OWN SOONER. ALSO; ACFT Y COULD HAVE NOTICED HOW CLOSE WE WERE BEFORE TAKING THE RWY OR THEY COULD HAVE REFUSED THE TKOF CLRNC; FORCING US TO GO AROUND BUT NOT HAVING TO WORRY ABOUT 2 ACFT OVER THE RWY AT ONCE.

Data retrieved from NASA's ASRS site as of January 2009 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.