 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 captain reported multiple incidences of close proximity events with other aircraft while on parallel approaches at den.
| Attributes | |
| ACN | 1522423 |
| Time | |
| Date | 201802 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | DEN.Airport |
| State Reference | CO |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
Denver converging visual approach 16L/16R: conditions were cavu and den approach cleared us for the visual and assigned a heading for us to join the final to 16R. We complied. Approach advised us of traffic landing on 16L and we called it in sight. It soon became obvious to us that; once again; den approach timed this merge perfectly; as in perfectly bad with no lateral or vertical offset. We set our TCAS to TA as is procedure for these two particular runways.we turned to join the 16R final and upon rolling out noticed the (other carrier) closer to us than was anticipated. We altered our track slightly right of the localizer course to maintain adequate space. Approach control advised us to contact tower; and I did not respond because I was too busy trying to ascertain if the (other carrier) aircraft was going to merge with us. Approach called us again and I switched over to tower after admonishing him for this unnecessary event. Denver tower issued a 'traffic alert' to the (other carrier) aircraft and they acknowledged that they had us in sight. They adjusted course and we both landed uneventfully.
Original NASA ASRS Text
Title: B737 Captain reported multiple incidences of close proximity events with other aircraft while on parallel approaches at DEN.
Narrative: Denver converging Visual Approach 16L/16R: Conditions were CAVU and DEN Approach cleared us for the visual and assigned a heading for us to join the final to 16R. We complied. Approach advised us of traffic landing on 16L and we called it in sight. It soon became obvious to us that; once again; DEN Approach timed this merge perfectly; as in perfectly bad with no lateral or vertical offset. We set our TCAS to TA as is procedure for these two particular runways.We turned to join the 16R final and upon rolling out noticed the (other carrier) closer to us than was anticipated. We altered our track slightly right of the localizer course to maintain adequate space. Approach Control advised us to contact Tower; and I did not respond because I was too busy trying to ascertain if the (other carrier) aircraft was going to merge with us. Approach called us again and I switched over to Tower after admonishing him for this unnecessary event. Denver Tower issued a 'traffic alert' to the (other carrier) aircraft and they acknowledged that they had us in sight. They adjusted course and we both landed uneventfully.
Data retrieved from NASA's ASRS site 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.