37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 882564 |
Time | |
Date | 201004 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | DEN.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 115 Flight Crew Type 115 |
Person 2 | |
Function | Pilot Not Flying First Officer |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Inflight Event / Encounter Other / Unknown |
Narrative:
We were cleared for a visual approach to land 16R at dia and were also advised of company traffic landing 16L (the company traffic was slightly above and behind us landing the parallel runway) which we did have in sight. At approximately a 3-mile final; we got an RA warning advising us to descend. We had both the runway and traffic in sight. According to the den commercial chart; 'due to the fact that 16R and 16L are separated by only 2500 feet; there is an increased possibility of TCAS TA's or RA's within 10 NM from the FAF to the FAF for 16L and 16R; especially during periods of high traffic density.' the RA advisory advised us to descend; which we were already doing; and since we had both the traffic and airport in sight and since we were already in close proximity to the ground and airport; I decided to continue on the glideslope and we landed without further incident. The only thing I might suggest is that when doing parallel approaches to 16L and 16R at den that perhaps the transponder not be on TA/RA to prevent a possible dangerous higher than normal rate of descent in close proximity to the ground and airport.
Original NASA ASRS Text
Title: A B737 flight crew on a visual to 16R at DEN took avoidance action in accordance with a TCAS RA and elected to continue the approach rather than go-around.
Narrative: We were cleared for a visual approach to land 16R at DIA and were also advised of Company traffic landing 16L (the company traffic was slightly above and behind us landing the parallel runway) which we did have in sight. At approximately a 3-mile final; we got an RA Warning advising us to descend. We had both the runway and traffic in sight. According to the DEN commercial chart; 'Due to the fact that 16R and 16L are separated by only 2500 feet; there is an increased possibility of TCAS TA's or RA's within 10 NM from the FAF to the FAF for 16L and 16R; especially during periods of high traffic density.' The RA Advisory advised us to descend; which we were already doing; and since we had both the traffic and airport in sight and since we were already in close proximity to the ground and airport; I decided to continue on the glideslope and we landed without further incident. The only thing I might suggest is that when doing parallel approaches to 16L and 16R at DEN that perhaps the transponder not be on TA/RA to prevent a possible dangerous higher than normal rate of descent in close proximity to the ground and airport.
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.