Very close call: reported to UA
Feb 20, 2022, 4:13 pm
#46
Join Date: Aug 2008
Location: SF Bay Area
Programs: UA 1K, Hyatt Globalist, Virtuoso Travel Agent, Commercial Pilot
Posts: 2,117
I wouldn't assume that. Legitimate TCAS RAs are rare but they do happen and they rarely make the news. It would be a pretty big stretch to believe that both pilots in each of the two aircraft, ATC, and TCAS all missed the incident though, especially at night when it is trivially easy to visually pick out other aircraft. (And given that none of the pilots took any action to avoid the potential collision, one has to assume that all the pilots, ATC, and TCAS all missed the incident.)
Feb 21, 2022, 4:27 am
#47
Join Date: Jul 2012
Posts: 1,115
Note it's not Aviation Herald or anything like that; while those are great resources, it's a 3 or 4 letter agency that maintains this database.
Feb 21, 2022, 4:36 am
#48
Join Date: Feb 2015
Programs: united
Posts: 1,636
FWIW when the Gol hit the Embraer, neither crew knew they had hit another aircraft. We have the tapes to prove this.
Feb 21, 2022, 8:20 am
#49
Join Date: Dec 2004
Location: NYC, LON
Programs: *
Posts: 2,771
i was seated in 1A in on the left of the CRJ200. I saw the other aircraft appear beneath us and it appeared to my right and went to the limit of my peripheral vision to the left in a near instant. I could clearly resolve the jet wake after it went by and we crossed it a half second later if I had to try to time it. It crossed the direction of travel from 1 to 7 o’clock. The size of the aircraft completely filled the small window in length. I was plastered to the window for whatever reason.
Feb 21, 2022, 8:24 am
#50
Join Date: Sep 1999
Location: SF Bay Area
Programs: UA 1K MM, Accor Plat, Htz PC, Natl ExEm, other random status
Posts: 2,876
I believe there is a publicly accessible database where these incidents - if reported - would end up (duly anonymized). I know it has been posted here in the UAL forum but I can't immediately find it.
Note it's not Aviation Herald or anything like that; while those are great resources, it's a 3 or 4 letter agency that maintains this database.
Note it's not Aviation Herald or anything like that; while those are great resources, it's a 3 or 4 letter agency that maintains this database.
Not every incident is reported, though.
Feb 21, 2022, 10:26 am
#51
Join Date: Jan 2009
Location: IAH/EWR-LGA/MIA
Programs: UA Global Services 3.2 MM, Marriott Bonvoy Lifetime Titanium Elite, AA Exec Plat
Posts: 2,505
Feb 21, 2022, 11:27 am
#52
Join Date: Feb 2002
Location: BNA
Programs: HH Gold. (Former) UA PP, DL PM, PC Plat
Posts: 8,184
That was a very unusual set of circumstances.
Brazilian ATC had forgotten about the biz jet. They were in a non-radar area separation should have been provided based on position reports. The biz jet's F/O had accidentally turned off their transponder so the 737's TCAS didn't see them. If they were in an area of radar service, the controller would have seen the primary radar target and the ATC computer would have continued to track it. The biz jet's crew past a fix where there was a planned climb due to a course change. They should have requested the altitude change and, at that time, would have realized that they had lost communication with ATC. They didn't, and that left them at the wrong altitude for direction of flight which was what put them head-on with the 737 that was at the proper altitude.
Brazilian ATC had forgotten about the biz jet. They were in a non-radar area separation should have been provided based on position reports. The biz jet's F/O had accidentally turned off their transponder so the 737's TCAS didn't see them. If they were in an area of radar service, the controller would have seen the primary radar target and the ATC computer would have continued to track it. The biz jet's crew past a fix where there was a planned climb due to a course change. They should have requested the altitude change and, at that time, would have realized that they had lost communication with ATC. They didn't, and that left them at the wrong altitude for direction of flight which was what put them head-on with the 737 that was at the proper altitude.