Rob2507 From United States of America, joined Jan 2001, 160 posts, RR: 0 Posted (6 years 2 months 2 weeks 1 day 7 hours ago) and read 2121 times:
Ledger Exclusive - 2 JETS NEARLY COLLIDE OVER HULL
By STEVE ADAMS
The Patriot Ledger
BOSTON - A Delta Air Lines jetliner aborted its landing at Logan International Airport this week after nearly colliding with a regional jet over Hingham Bay.
A collision alert sounded in the cockpit of Delta Flight 1637 at 4:37 p.m. Tuesday after it came too close to a Delta Connection flight operated by Chautauqua Airlines, FAA spokesman Jim Peters said.
In a transmission captured on the aviation Web site liveatc.net, the Delta pilot notified the Logan tower of the close call after he aborted the landing.
‘‘Tower, (this is Delta flight) 1637, we’re level at 3,000 (feet). That traffic was just about 100 feet below us.’’
A passenger on the Delta jet, Brian Phillips of Salt Lake City, said the pilot later told passengers the planes had come within 200 to 300 feet of each other. The pilot seemed to blame air traffic controllers for the close call, Phillips said.
AviationAddict From United States of America, joined Feb 2006, 539 posts, RR: 0 Reply 2, posted (6 years 2 months 2 weeks 1 day 6 hours ago) and read 1969 times:
I don't understand why the Delta pilot needs to submit a report but the Delta Connection pilot does not. Based on the article it seems like the FAA is trying to blame the 757 pilot, but it also seems like the E145 aircraft was behind the 757, so shouldn't the pilot of that aircraft carry more responsibility? I mean, if you're behind another aircraft, how do you allow yourself to close to within a few hundred feet without trying to avoid a collision? Seems like there's more to this story than is being reported.
...which indicates that TCAS lit up with an alert while the two airplanes were on PARALLEL, visual approaches to the airport, most likely Runways 33L and 32. (or the 4's)
Given the FAA is not investigating, and the pilots aren't required to submit any reports, I'd say this was just a flub. I'd imagine that in a high-traffic terminal area, TCAS would be turned off or desensitized, but from what I understand is that pilots are obligated to abide by a TCAS warning, so that is why the Delta had to abort even though there was legitimate visual separation on the approach.
RandyWaldron From United States of America, joined Mar 2006, 324 posts, RR: 3 Reply 4, posted (6 years 2 months 2 weeks 1 day 3 hours ago) and read 1763 times:
This situation is being blown way out of proportion. If you listened to the tower frequency that day, or, if you listened to the ATC tapes on LiveATC.net, you would have clearly heard the DL (Mainline) pilot state: "We had to comply with an RA.."
"RA" is the acronym for Resolution Advisory. An RA is a message generated by the TCAS system to indicate another aircraft is approximately 20 seconds from the closest point of approach. The RA provides a vertical restriction or vertical guidance maintain or increase separation from the traffic.
Pilots are compelled to comply with Resolution Advisories when the Transponder/TCAS system issues them. However, stating that these jets nearly collided is a bit misleading. The more factual story is that these aircraft were on converging visual approaches, were a little too close to each other (laterally) and the vertical separation was a few hundred feet. TCAS then issued a RA, and the DL Mainline pilots complied.
RandyWaldron From United States of America, joined Mar 2006, 324 posts, RR: 3 Reply 5, posted (6 years 2 months 2 weeks 1 day 3 hours ago) and read 1742 times:
Quoting AviationAddict (Reply 2): I don't understand why the Delta pilot needs to submit a report but the Delta Connection pilot does not.
It is quite simple. The DL Mainline pilots responded to and initiated evasive maneuvers in compliance with a Resolution Advisory issued by TCAS. Therefore, they are compelled to submit a report as they complied with TCAS instructions.