 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Erj-190 flight crew reported getting an RA caused by an aircraft on a visual approach on the parallel runway into bos.
| Attributes | |
| ACN | 1252986 |
| Time | |
| Date | 201504 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BOS.Airport |
| State Reference | MA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 190/195 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Conflict Airborne Conflict |
Narrative:
We were on the ILS 4R approach to bos in good VMC conditions. The approach controller on frequency 126.5 reported traffic to our left that had us in sight and was landing on runway 4L. Although we saw a target on the TCAS to our left and below us; we were not able to locate the aircraft visually. Approach control switched us to the tower on frequency 132.22. Shortly thereafter; at approximately 3500 feet MSL; we received a TCAS traffic advisory (TA); then an resolution advisory (RA); but were still not able to see the aircraft. I initiated a climb in response to the RA and the captain reported the RA to the tower. When clear of conflict; I returned to the glideslope and a stabilized approach and continued to a landing. We never did see the aircraft.an aircraft on a visual approach to runway 4L apparently strayed into the approach corridor for runway 4R. The aircraft either did not have us in sight or did a poor job of maintaining visual separation.approach control could possibly stagger the arrivals to the parallel runways to provide better separation even though visual separation is already in use.
Original NASA ASRS Text
Title: ERJ-190 flight crew reported getting an RA caused by an aircraft on a visual approach on the parallel runway into BOS.
Narrative: We were on the ILS 4R approach to BOS in good VMC conditions. The approach controller on frequency 126.5 reported traffic to our left that had us in sight and was landing on runway 4L. Although we saw a target on the TCAS to our left and below us; we were not able to locate the aircraft visually. Approach control switched us to the tower on frequency 132.22. Shortly thereafter; at approximately 3500 feet MSL; we received a TCAS Traffic Advisory (TA); then an Resolution Advisory (RA); but were still not able to see the aircraft. I initiated a climb in response to the RA and the captain reported the RA to the tower. When clear of conflict; I returned to the glideslope and a stabilized approach and continued to a landing. We never did see the aircraft.An aircraft on a visual approach to runway 4L apparently strayed into the approach corridor for runway 4R. The aircraft either did not have us in sight or did a poor job of maintaining visual separation.Approach control could possibly stagger the arrivals to the parallel runways to provide better separation even though visual separation is already in use.
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.