37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 935259 |
Time | |
Date | 201103 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MDW.Airport |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Aircraft 2 | |
Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Person 1 | |
Function | Pilot Not Flying First Officer |
Experience | Flight Crew Last 90 Days 334 |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 260 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Miss Distance | Horizontal 500 Vertical 400 |
Narrative:
I was the pilot not flying. We were cleared for and established on the mdw ILS/localizer runway 4R with a planned circle to land on runway 13C. We contacted the midway tower at FAF/ermin as directed. We were instructed by the midway tower to circle to and continue (no landing clearance) for runway 13C and advised of a rj (regional jet) also on the modified base to final for runway 13C (ahead of us) and a {another carrier} approaching runway 13R. From inside ermin; the pilot flying selected an approximately 000 degree heading and descent to 1;700 ft MSL. As we began the turn to the heading; I quickly loaded the RNAV (GPS) Z to runway 13C into the FMC to provide some course and glide path guidance to runway 13C (localizer and G/south were NOTAM'd out for runway 13C). As we passed approximately west of mdw; a flock of geese flew approximately 300 ft below us and I reported them to the midway tower. Apparently the pilot flying missed or did not fully comprehend the original midway tower instructions and my reply that our clearance was to continue to runway 13C and to look for the rj ahead to follow. The pilot flying began a short right base for runway 13C and called for the before landing checklist. I assumed the pilot flying had the rj in sight and had not advised me. As we completed the checklist; the midway tower asked something to the effect of; 'do you have the rj in sight?' they additionally stated something to the effect of; '(we) are turning base inside of the rj traffic and to stop our turn towards the runway.' then; one of the pilots on the rj came over the midway tower frequency and advised us something to the effect of; 'immediately turn to a downwind heading to avoid our flight path.' the pilot flying immediately began a left turn back to an approximately 300 heading and; as we began the turn; I visually acquired the rj at our 10 to 11 o'clock position; approximate co-altitude and probably 2;000 ft and closing as the rj continued his final approach to runway 13C. I would estimate we passed 500 ft or less from the rj on a reciprocal heading. As we passed; we received both TCAS TA's and RA's to climb immediately; which were complied with. After the TCAS RA's were resolved; we turned right to join the final approach to runway 13C. We were cleared to land on runway 13C by the midway tower and landed without further event. To the best of my knowledge; no other radio calls were given by ATC (midway tower); the rj; or any other aircraft regarding this event.the midway tower could have been more definitive with their initial call; 'company XXX; continue circle to runway 13C; you are number two following a rj (point out); additional traffic is a {another carrier} to runway 13R. Report the rj in sight. 'I should have used the TCAS display earlier to help me attempt to visually acquire the rj traffic. The flock of geese did take my visual scan away momentarily. I should have queried the pilot flying to ensure he had the preceding rj in sight as he began his base to final turn. I could have prioritized/handled my task management duties better (clear of traffic/birds; configure the aircraft; run the before landing checklist; communicate with ATC; etc...) aviate; navigate; and communicate! Never; ever assume. If in doubt; ask/confirm!
Original NASA ASRS Text
Title: B737 flight crew reports a conflict with another aircraft during a circle to land maneuver from Runway 4R to Runway 13C at MDW.
Narrative: I was the pilot not flying. We were cleared for and established on the MDW ILS/LOC Runway 4R with a planned circle to land on Runway 13C. We contacted the Midway Tower at FAF/ERMIN as directed. We were instructed by the Midway Tower to circle to and continue (no landing clearance) for Runway 13C and advised of a RJ (regional jet) also on the modified base to final for Runway 13C (ahead of us) and a {another carrier} approaching Runway 13R. From inside ERMIN; the pilot flying selected an approximately 000 degree heading and descent to 1;700 FT MSL. As we began the turn to the heading; I quickly loaded the RNAV (GPS) Z to Runway 13C into the FMC to provide some course and glide path guidance to Runway 13C (LOC and G/S were NOTAM'd out for Runway 13C). As we passed approximately west of MDW; a flock of geese flew approximately 300 FT below us and I reported them to the Midway Tower. Apparently the pilot flying missed or did not fully comprehend the original Midway Tower instructions and my reply that our clearance was to continue to Runway 13C and to look for the RJ ahead to follow. The pilot flying began a short right base for Runway 13C and called for the Before Landing Checklist. I assumed the pilot flying had the RJ in sight and had not advised me. As we completed the checklist; the Midway Tower asked something to the effect of; 'Do you have the RJ in sight?' They additionally stated something to the effect of; '(We) are turning base inside of the RJ traffic and to stop our turn towards the runway.' Then; one of the pilots on the RJ came over the Midway Tower frequency and advised us something to the effect of; 'Immediately turn to a downwind heading to avoid our flight path.' The pilot flying immediately began a left turn back to an approximately 300 heading and; as we began the turn; I visually acquired the RJ at our 10 to 11 o'clock position; approximate co-altitude and probably 2;000 FT and closing as the RJ continued his final approach to Runway 13C. I would estimate we passed 500 FT or less from the RJ on a reciprocal heading. As we passed; we received both TCAS TA's and RA's to climb immediately; which were complied with. After the TCAS RA's were resolved; we turned right to join the final approach to Runway 13C. We were cleared to land on Runway 13C by the Midway Tower and landed without further event. To the best of my knowledge; no other radio calls were given by ATC (Midway Tower); the RJ; or any other aircraft regarding this event.The Midway Tower could have been more definitive with their initial call; 'Company XXX; continue circle to Runway 13C; you are number two following a RJ (point out); additional traffic is a {another carrier} to Runway 13R. Report the RJ in sight. 'I should have used the TCAS display earlier to help me attempt to visually acquire the RJ traffic. The flock of geese did take my visual scan away momentarily. I should have queried the pilot flying to ensure he had the preceding RJ in sight as he began his base to final turn. I could have prioritized/handled my task management duties better (clear of traffic/birds; configure the aircraft; run the Before Landing Checklist; communicate with ATC; etc...) Aviate; Navigate; and Communicate! Never; ever assume. If in doubt; ask/confirm!
Data retrieved from NASA's ASRS site as of April 2012 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.