 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737NG responded to a TCAS RA while on final approach to pdx.
| Attributes | |
| ACN | 844870 |
| Time | |
| Date | 200907 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | PDX.Airport |
| State Reference | OR |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
On visual approach to pdx runway 28L; inside outer marker; at app. 1;800'; talking to tower; cleared to land. Noticed traffic alert from TCAS. Advised pilot flying to be alert for possible traffic conflict. Traffic was on converging path at approximately the same altitude. TCAS traffic alert turned to resolution advisory (RA). Traffic was acquired visually at same time as RA received. Instructed pilot flying to immediately climb. Conflict was resolved when traffic passed under and behind us. The avoidance maneuver resulted in an unstable approach and we decided to execute a go-around/missed approach. Traffic was a small single engine; low-wing aircraft; ahead on our left side. The aircraft was approaching us on a converging path; and it seemed like it would cross the final approach path to runway 28L at our approximate location; and at the same altitude. The traffic took no corrective action to avoid conflict; leading us to assume that he never saw us. I also think that the other aircraft must have been unaware of its proximity to pdx airport; since it was on a path to cross final approach to the active runway inside the final approach fix at our approximate altitude.
Original NASA ASRS Text
Title: A B737NG responded to a TCAS RA while on final approach to PDX.
Narrative: On visual approach to PDX runway 28L; inside outer marker; at app. 1;800'; talking to tower; cleared to land. Noticed traffic alert from TCAS. Advised pilot flying to be alert for possible traffic conflict. Traffic was on converging path at approximately the same altitude. TCAS Traffic Alert turned to Resolution Advisory (RA). Traffic was acquired visually at same time as RA received. Instructed pilot flying to immediately climb. Conflict was resolved when traffic passed under and behind us. The avoidance maneuver resulted in an unstable approach and we decided to execute a go-around/missed approach. Traffic was a small single engine; low-wing aircraft; ahead on our left side. The aircraft was approaching us on a converging path; and it seemed like it would cross the final approach path to RWY 28L at our approximate location; and at the same altitude. The traffic took no corrective action to avoid conflict; leading us to assume that he never saw us. I also think that the other aircraft must have been unaware of its proximity to PDX airport; since it was on a path to cross final approach to the active runway inside the Final Approach Fix at our approximate altitude.
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.