 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier on vectors for approach to iad runway 1C elects to execute a go-around when ATC advised parallel runway traffic was landing runway 1R. Reporter questions separation and controller performance.
| Attributes | |
| ACN | 826586 |
| Time | |
| Date | 200903 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | IAD.Airport |
| State Reference | DC |
| Aircraft 1 | |
| Make Model Name | B737-500 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach Landing |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain |
| Experience | Flight Crew Last 90 Days 250 Flight Crew Total 13000 Flight Crew Type 4000 |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
During descent; the controller left us high and fast (5;000 ft and 250 KTS assigned) approaching the marker (skins). We called 'field in sight' to ease the burden on the controller and take responsibility for the high/fast situation he got us into. His response 'roger' (read -- no approach nor descent nor slowing clearance). Finally he asked if we had traffic at our 10 o'clock position in sight. We responded we did (it appeared that the traffic in question was going to runway 1L). At this point he said 'maintain visual; cleared for the approach runway 1C; traffic is for runway 1R.' 1R!!!! I simply came on the radio and said 'this won't work' to silence for a response. He proceeded to give us vectors for another approach; to which I questioned every turn searching the sky for other traffic. This controller needs a few weeks in the simulator to get back up to speed. When I called to talk to the supervisor; his response was so lackadaisical that there is no question in my mind where the haphazard attitude in the controller came from. It was beyond unsafe!
Original NASA ASRS Text
Title: Air carrier on vectors for approach to IAD Runway 1C elects to execute a go-around when ATC advised parallel runway traffic was landing Runway 1R. Reporter questions separation and Controller performance.
Narrative: During descent; the Controller left us high and fast (5;000 FT and 250 KTS assigned) approaching the Marker (SKINS). We called 'field in sight' to ease the burden on the Controller and take responsibility for the high/fast situation he got us into. His response 'Roger' (read -- no approach nor descent nor slowing clearance). Finally he asked if we had traffic at our 10 o'clock position in sight. We responded we did (it appeared that the traffic in question was going to Runway 1L). At this point he said 'maintain visual; cleared for the approach Runway 1C; traffic is for Runway 1R.' 1R!!!! I simply came on the radio and said 'This won't work' to silence for a response. He proceeded to give us vectors for another approach; to which I questioned every turn searching the sky for other traffic. This Controller needs a few weeks in the simulator to get back up to speed. When I called to talk to the Supervisor; his response was so lackadaisical that there is no question in my mind where the haphazard attitude in the Controller came from. It was beyond unsafe!
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.