UPDATE!: 9:20 That was ANOTHER aircraft on the ground at LGA who wanted to know the reasons for the Go-Arounds so he could make a better Go/NO Go Decision. He elected to NOT GO until the weather (winds) improved. Windshear needs to be accurately PIREDed by Aircrews to help make informed decisions about the operation. Jb 4/7/24
I wish there was a PIREP broadcasting service on either ATIS or in a parallel channel so aircrews can get the latest update before a go/no go decision is made in dodgy weather.
Not a pilot, but I am a Radio Amateur. So apologies if this sounds like a stupid question: Was the aircraft possibly aligning itself with a sidelobe of the guidance beam? That could explain the deviations. Thanks.
Yes Juan, they pilots usually give a Windshear report after rollout. We have given one at LGA of 10-15kts. It can be tricky. Just the fact that Pireps are being given is enough to warn the pilots of the presence of Windshear as well as it being a positive or negative. Pireps are put on Wx sites and are relayed by ATC. It will be included in ATIS if the airport is reporting it. Winds can change a lot in a short period of time as in x-wind and an aircraft might be out of limits after lining up on the runway. A lack of situational awareness is going to be a factor here.
Female was flying thr approaches that's why. Pilot flying doesn't talk. After 2 failures and one of them being so massively pathetic it's ASTONISHING the pilot flying is even a fkn pilot much less airline pilot, the captain took over which is why the female was speaking on southwest after the second pathetic attempt
@@wturn5354I wonder if she wasn't the controller handling finals, and didn't even have them on a screen (for ID), but just saw them out the window?😮 Concerning that none of the bells and whistles went off!
@@dosgosyes, and not using a call sign frequently results in the pilot asking if that call was for them, or another pilot may ask as well and a LOT of time is wasted! There is a reason flights have call signs!
Some people owe a big thank you to the controller, she definitely saved the day and peoples lives, potentially including hers and the other controllers. What a way to start a shift, seeing a Boeing emerge from the mist heading straight towards your tower !
Sir I would like to ask you a question. Do we have to many planes to Handel? Even if these pilots are the blame is it time to reduce the number of take offs and landings?
That controller deserves an award. She very likely saved hundreds of lives in that moment, possibly including her own. What a scary situation, and thank goodness for her quick and clear reaction.
@@wturn5354 🤦♂️ There’s always one if you, isn’t there? The time required to figure out and say their callsign might’ve been the difference between recovery and collision. The plane on terminal descent got the message and acted immediately. You should watch this video again and listen to Juan’s detailed breakdown to understand how close they were to ending up in a ball of flames.
ASDE stands for Airport Surface Detection Equipment....or at least it did 12 years ago when I retired. I am pretty sure that the "new" controller was receiving a change of controller briefing from the "old" controller when she saw that Southwest was not where they should have been so she took appropriate action. Well done!
I would be interested to learn how controller-to-controller briefings occur at an area as demanding and critical as this is. How do you hand off such busy airspace without reducing your situational awareness? Is there an overlapping handoff, where controller taking over just observes for 30 mins or something so you can minimize the words that need to be spoken off air? I agree this controller saved the day. A lot more is needed to determine what happened in the airplane.
@@seanur2414 The relieving controller observes for several minutes then will say “I got it”, then the controller that was relieved will stay for several minutes after to ensure integrity.
Thank goodness that controller looked out the window. I suspect that when starting a shift there's a lot to review on the computer screen to understand where everyone is at. That could have been a major disaster destined for a movie script.
Same can be said about machines. I would argue that machines helped with more landings than they hurt however I'm not at all suggesting removing humans.
FALCON is a radar replay tool that we controllers have. It's like having Victor put a video together for us except that it's much quicker, has more detail in several ways, but it doesn't come with subtitles. We controllers use FALCON to do radar replays somewhat regularly. Sorry that we FAA people speak in acronyms like a second language. (Though I am current FAA, my views and opinions are expressed in a private capacity).
Brand new GA pilot here after happily retiring early from Pfizer, so bear with me. Do Southwest 737s have Cat III autoland capabilities in their aircraft? Any ideas why the La Guardia plates say "Autopilot coupled approach not authorized for Runway 04"? Any ideas what Southwest's minimum are?
@@PfizerRN_NavyReserveCaptain Juan explains it in the video. First of all, no autoland on Rwy 4. Best rumour is that the localizer is known to get squirrly near the ground and would cause too much movement of a coupled aircraft.
@@PfizerRN_NavyReserveCaptain LGA is known to have problems with magnetic compass interference due to how it was built, using fill from Rikers over steel-frame pilings. I don't know if ILS anomalies are also connected to this problem.
I’ve landed probably 180 times of in LGA, in good and bad weather, minimum visibility, windy, rainy and very snowy-in Barons, bonanzas, DC9’s, MD80’s, 727’s and 757’s and 767’s. It’s a very demanding airport, vfr and especially ifr-then add snow! Most airline pilots are intimidated before they even get close to the airport. The secret is to know your airplane, always be at the appropriate speed, land in the first 1000’ and don’t float in the flare. If you can do ALL that, you are not intimidated! Glad I’m retired, and don’t have to endure that any longer🤪
If that is truly a “secret” it’s time to inform all pilots! The consequences of not being aware of this secret could potentially be the difference of success or failure🙏
Juan, I think it's a true testament to the quality of your reporting that tower controllers are not only here watching your videos but also willing to stick out their necks to comment.
I'll wager the oncoming controller was standing right there at the controller spot she was taking long enough to witness the first go-around and was looking out the cab window for the aircraft when it descended below the cloud layer. Standing in the background observing gives one the time and perspective to sense these types of things in all situations in life.
Could very well be. It is a great save. Controllers are regularly reminded that during and immediately after Position Relief Briefings (PRBs) the risk of a mistake or oversight is much higher and we are trained to be even more vigilant because of it. During PRBs there is a lot of information being exchanged verbally, while traffic continues to move, and it takes careful focus to stay on top of things.
JetBlue immediately made the right call on the Low Alt alert from the tower, don't try to fix it just go around, very prudent. There's no harm, no foul on a decision to go around.
They almost wiped out a neighborhood in Queens! Looking at the ADS-B for 17:01:28Z, they were at 275 feet pressure altitude and STILL DESCENDING at 576 feet per minute! KLGA altimeter was 29.79, so that means they were at 135 feet MSL. Street level there is 27 feet MSL, so they were 108 feet above street level and maybe 75 feet above roof level! Well, at least their static port was! I wonder how far below the static port their wheels were? If they had delayed the go-around for a few more seconds...😮
Good call about the equipment being that high.😅 But you have to measure it from the "sensor," which could be higher or lower inside the aircraft than the actual static port.
@@johnhill2927 Ah, good point about the location of the actual pressure sensor. I also downloaded the EGM96 corrected GPS kml file from ADS-B. It shows a minimum altitude of 47 meters, or basically 154 feet MSL. I suppose GPS altitude is not exactly the same as antenna height? Is there some additional error because the velocity factor of the GPS antenna cable is less than 1? Or is the GPS solution made right at the antenna by embedded electronics?
@@Highside713 People in Queens are so used to low flying planes that this may not have registered, so they didn't review their security cams/doorbell cams.
MOR is the actual report name-“Mandatory Occurrence Report”, and the FLM is the ATC Front Line Manager-the Sup. A PRB is a position relief briefing-the exchange/briefing that happens when a new controller takes over a position from the one leaving.
@@caroltlw Local control (tower) is nearly all visual-primary responsibility is runways. There is likely radar available to the LGA tower controllers, but it’s for situational awareness, not radar services. That tower is so busy, it’s not likely they would have time to issue low altitude alerts based on that. If they got one, they would look out the window and verify before saying anything-just like what this controller did. I’m not aware that any alarms like that can be “turned off”. ATC is a very “CYA” activity. The default would be to warn/notify a pilot if there was any concern, rather than to mute anything that could end up biting you in the rear end.
@@theflyingbisq OK, I was confused by the reference in the report to the ADSE/ATAP alert not going off and being investigated. I thought maybe that was something in the tower. Maybe "reset" is a better word for what I was thinking... flashing lights or something.
@@caroltlwit’s a good question. It may have been so far east of the taxiway that ATAP didn’t make a prediction that the inbound was lined up with the taxiway. I’m not that familiar with the technical aspects of it. It’s only available at like 40 facilities.
By the time the controller got out the words SWetc, which takes about three seconds, the plane would be about 600 feet closer. Sticking to your formality in this case could have killed everybody on board and more on the ground. When you see a brick falling on someones head, Do you say” Hey over there, A brick is falling on you” or do you scream watch out. It doesn’t matter if everyone has a look. There’s a time for formality and a time for commonsense. You don’t get consultation times in such an event. Lucky the Controller just gave ashout out instead of giving a formal call sigm.
Amazing that the airplane was at 100 feet above the ground so far off course. Good job by the ATC controller taking immediate action during a shift change.
But if you’re breaking out of the soup at 5-600’, how do you get down to 100’ without noticing what is wrong? Descending at 500’/min, going from 500’ to 100’, that should easily be 30+ seconds in the clear, even accounting for any loss of altitude while spooling engines up.
Female was flying thr approaches that's why. Pilot flying doesn't talk. After 2 failures and one of them being so massively pathetic it's ASTONISHING the pilot flying is even a fkn pilot much less airline pilot, the captain took over which is why the female was speaking on southwest after the second pathetic attempt
Retired airline Captain, I have flown many many times into KLGA. Juan, please note that the ILS Hold Short line on Taxiway Bravo for ILS 4 is not at the runway threshold. It is well short of where ILS Hold Short lines are normally located for most runways. This makes me wonder about the the deviations and the number of Go-Arounds. It may be that there was airplane or vehicular traffic encroaching past the ILS Hold Short marker.
The reason for the uncoupled approach with no AP on ILS 04 is because of the interference of the rwy 13 system or building at the intersection of rwy 13. I see VASA had the answer. I've flown the ILS 04 into LGA at mins, but the wx was not as windy although have flown into LGA when the wind was bad which is often. Disengaging the autopilot as soon as you intercept the LOC is pretty straight forward flying even if this is mins wx. That's our job! If your in an uncontrolled approach then you initiate a go-around. If you miss twice and wx is really bad you divert to your alternate. This is all textbook stuff. After your 2nd approach your probably at BINGO fuel anyway, so off to ALT, notify ATC and Company and get the heck out of it. Windshear is not fun at low altitude. Not too sure why SW was so far off track on the LOC. Did they intercept the false reading? ILS instrument equipment faulty? You intercept the LOC within 10 degrees of centreline 18nm out. Not a false Glideslope as they seemed to be at right height upon breakout. But that far off runway to the right is got to be at least a dot out? Glad to see they diverted and landed safely in PHL. I think they have some questions to answer. Why that far off centreline and not know it?
Based on other accidents I wonder if there were 4 eyes looking for the airport instead of 2. Seems like the stress and workload after a miss might have contributed to a loss of situational awareness.
I was a controller in the old LGA tower, which was much closer to the runways than the current tower. I remember at least a couple times when we were scared that a missed approach/go around might hit the tower!
that controller was that called out the go around is a hero for noticing and acting on it. that jet was definitely crashing into the houses before the airport
Nonsense! The crew was probably already taking corrective action since they had broken under IMC and probably were quite shocked to see the tower ahead.
That lady ATC was very firm in her call and a hero, pilot unable to explain his huge near miss and near crash. I think that pilot will be driving Taxis in NY from here on.
Driving a taxi in Manhattan would be more difficult and more stressful than landing at LaGuardia...maybe he could be an engineer's mate on MV Dali...erp...quality control at Boeing?
She definitely saved the day! I imagine how I would have been shaking after an incident like that. So great it worked out good and everyone could walk away harmless with the new things to learn!
This was so incredibly close to being a major accident. If that new controller wasn't so aware, assertive and transmitting a very clear no nonsense instruction, a few seconds later we would be talking about hundreds dead. There was 5 seconds at most in that becoming global news.
Wonder how many other planes in the area pulled up at her command. Never said who she was or who she was talking to. And she did a great job. Probably saved many lives. Tell her to take a deep breath. In only 8 hours and 59 minutes, counting lunch, she can call it a day.
As a retired SWA 73 capt. Hand flown ILS to mins would be a HUD flown ILS. So how can the crew be that far displaced? Twice? Sure the WX was a factor, judging by the number of go arounds. Hopefully the capt pulled the recorder CB.
AFS Guidance Engineer here.. this looks like a typical case of LOC deviation beyond 1 dot.. The fact that the chart published AP use not authorized, and the fact the flight crew did not see this deviation on the ND, points us to believe that there was some sort of interference in the LOC signals. Meaning AP was most probably ON and the aircraft was correctly "tracking" the LOC signals, however this LOC signal was itself "bad or incorrect", but neither the AP computer nor the pilots know this. This interference (deviation is LOC signals) can be due to poor shielding of the LOC antennae (at the end of the RWY 04) due to ground operations (aircraft taxiing in front of the antenna). LGA is located in a very dense (EM radio signals) area with TEB and JFK in close proximity, which could be prone to frequent signal interferences especially in case of enhanced LOC capture approaches. I was once analysing an incident report from Qatar Airways captain flying in approach to DOH RWY 34R, and the aircraft was targeting (nose alligned) straight to the Banana Island and clearly deviating from runway 34R centerline.
@@FamiliarAnomaly Who said anything about it being digital? If you're not aware of how ILS works, maybe google "How does ILS work". Wikipedia has a good article on it. Not sure why you're assuming it's digital?
@@FamiliarAnomaly The localizer is an array of antennae that all transmit on slightly different frequencies, and the plane triangulates from them. If one or more of them are blocked by another plane, garbage, trucks, or even too much snow, then the triangulation can be wrong and distort the inferred geometry. The system uses the relative strength of each signal, not some coded message in 1s and 0s. So if a plane was taxiing too close, it could have sent that landing plane off in a veering direction but not any other plane that day. Also because other planes were following the rules and not using auto pilot.
This has happened before. I lived off the end of rwy 4 in Jackson Heights for 7 years. Normally aircraft would approach diagonally behind my building a several blocks to the west. However one evening back about 2010-2011 in similarly bad weather an aircraft came right over my building a lot lower than it should have. Then it happened 2 more times in a row. Looking at Juan's screen at 12:33 brought me right back as that would have been the same flight path as that night. Scared me enough where I wanted to call the Port Authority to report it but after the third aircraft I think they changed runways to 22. I also do not recall if the new tower was live yet. Thanks for the report.
I was out walking in that rain, right under the approach path that day in Brooklyn. Seeing the planes popping out of (and back in to) the clouds was cool! I may have even seen this flight, definitely saw some SW planes.
I once flew an ILS where the signal identified and it came in, but it was waaaaaay off. Having plates live as a gps reference was invaluable as you could see it tracking way left. Turned out, someone had hit the glide slip with a mower shortly before and threw it off. Pretty wild that we don’t have redundancy for ILS. At this point, we should have gps backed up reference systems to see redundancy early and continuously in the approach!
I think that call for the reason for the two go around was an internal coordination communication between local control and the approach control. That being said LGA can be tricky in that type of weather. All sorts of wind shear and you get rotor off of the buildings which can make for a rough day. The reason that the autopilot isn’t authorized is because there are two very busy roadways very close to the approach end of the runway. The Grand Central Parkway and inside the airport perimeter, the airport service road which is not controlled by ATC and particularly when any large vehicle crosses the extended center line on the service road the localizer will windshield wiper. Sometimes it can be very subtle and not easily detectable by the flight crew. After some 30 years of going in and out of there I’ve seen it all including many times having the loc needle bang from side to side which of course initiated a go around. The perimeter roadway is just beyond the ILS critical area and crosses the approach end of the runway.
@@GardenGuy1942 VASAviation posted this on Mar 25, two days after the incident occurred, and his ADS-B analysis the next day. Been waiting for a write-up on any investigation into this.
Thank you Juan for reporting on this, and indeed all of your aviation safety reports! And I also want to acknowledge the pilots in this report, all of them. They all responded correctly too! Not only the Southwest pilots, but also the other pilots who went around, and the other controllers too. This was just a very nasty time to be flying into LGA.
@@james_chatman This was apparently some type of CRM failure. The PM was not monitoring properly. Hopefully they'll find out why and it will be a lesson learned to avoid a future recurrence.
Possible explanation. Upon breaking out below the ceiling at about 600 feet, the pilot visually transitioned to what they thought was the runway. The transition from instruments to a visual on the runway is a critical phase, especially with reduced visibility as was the situation here. “Rabbit” lights, VASI/PAPI, and a quick peak at the ILS deviation bars can help avoid biting off on something that looks like a runway but isn’t (a taxiway, car lights, a roadway, etc.)
I was base at La Garbage back in the 80 with Eastern. Low visibility approaches were always a bitch because of turbulence, aircraft spacing Ney York traffic congestion. It has changed very little in the last 35 years. Not enough runways, too short runways and the added pressure of the whole situation. At least they took down the sky jump at the end of the runway into Flushing Bay.
Yep, I had caught Victor's (Vasaviation) post hours before! He was ON IT immediately!! Fully expected Juan to chime in, unless he was over the Pacific somewhere!!
Outstanding video and explanation. I've been a passenger flying into 4 at LGA, it felt like we were going to hit a building! I can't imagine how frightening it would be to miss that bad. Your video was clear and concise. I am very interested to learn more.
I live on Long Island and it was monsoon season on the day this occurred. I'm glad they made it to Philadelphia without further incidents. Thanks for your breakdown Juan. You and Victor are a great team 👍🏻
Victor from VASAviation did a follow up where he showed that the reason for the prohibitive on autopilot coupling is due to a hotel that was built that interferes with the localizer
That sounds suspicious, I’m not a pilot at all but you’d think they’d take that into consideration before building a hotel that could interfere with landing. Lol
Every directional antenna has a lobe. Also, RF ducking/reflection for the geography (body of water, building roof/wall materials). During my prior life performing tech ops in commercial broadcasting, I read some of the trade publications. There was an article on ducting, when a body of water causes undesired multipath reflection (false echoes). Another article on tower service maintenance personnel safety, where FM stations operating in the lowest FM frequencies must significantly decrease transmitter power to avoid cooking balls, whereas those in the 100's seemed to be a lesser personnel safety issue as the energy instead reflects. Horizontal ILS transmits at 108 to 112 MHz. So, now I am wondering if something temporarily blocked the directional ILS ground transmitters' antenna array, causing the aircraft ILS receiver to lock onto a lobe that reflects off the tower or water, coupled with not looking out the windshield (or nose cone visually blocking due to AoA).
Notice that after the second go around, different voice on the radio. Sounds like the PF and PM switched places. Perhaps the Captain took the controls. Just speculating.
11:46 With regard to the localizer getting wavy for the 04 approach, I think I can see the reason. Runway Drive passes directly in front of the right side of the localizer antenna array at the foot of the runway. The Q48 bus, and some airport shuttle buses and other tall broad sided vehicles pass directly in front of the line of sight of the localizer antenna. That's probably why the localizer antenna gets all "screwy" and you can't fly that approach autopilot coupled.
Actually, Runway Drive passes directly in front of the runway 22 localizer array. The runway 4 localizer array is located at the NE side of the runway, on the water.
LGA TWR dialogue at 9:34 sounds to me like "This guy was not aligned...He was, like, east of the final." It sounds like they were talking to a third party.
I think the center was asking the tower why there were two go arounds and tower responded that the plane was misaligned. Odd that it was picked up with other transmissions.
That controller needs to be recognized for her immediate and clear action. She prevented absolute certain carnage! Clearly, there are some definite shortcomings with critical equipment at that facility. Maybe this incident forces the necessary changes.
It's what air traffic controllers get paid to do.... To prevent exactly this sort of thing from happening. We don't need to give "atta-girls" and "atta-boys" to people who are just doing their job. 🤷♂️
@MrHimynameisdanny I actually NEVER do that, Danny. I just don't see the need to give accolades to public servants who we pay to sit on their asses most of the time, and then do a job when we need them to do it. It was all right there in the job description when they were hired. The sense of entitlement that people have nowadays is incredible.
PRB - Position Relief Briefing. A new controller was taking over the position, and the (required, and recorded) relief briefing took place from the controller being relieved to the oncoming controller
Ive done that approach for 30 plus years, and yes you do get loc scaling on the ILS 4. Its caused by a road near the loc antenna, that when trucks pass the antenna you get the scaling. The SW 737 most likly had the auto pilot on.
So, the ILS approach, which is certified as a precision approach, is anything but precision. One would wonder how this approach could be published when it is subject to anomalous behavior..
@@donallan6396 This is an autopilot limitation which the approach plate specifically states that "AUTOPILOT COUPLED APPROACH NOT AUTHORIZED". Whether or not you are using an autopilot has nothing to do with the precision of the approach. Some autopilots can have high gain when trying to track a localizer or glideslope signal which, if disturbed and very quickly goes full scale, the AP might aggressively maneuver the aircraft in an undesired state in order to catch it. These approaches are flown, tested, and retested by FAA "Flight Check" aircraft in order to maintain the integrity of instrument approaches.
Wow, this is quite distressing. I wonder since they were so far off course and so low, and if Autopilot was not on, would there be "pull up" or "terrain" warnings? At 100 ft, they were not only in danger of hitting the tower, they were right over homes or offices and risking barreling into those as well. That other ATC person really did save the day. Thanks, Juan, for the overview. I'm looking forward to more info when available.
Juan, thank you for explaining this incident and making it easy to understand , for a non-pilot aircraft enthusiast such as myself, as to exactly what happened .....great channel !!!
Just guessing here, but the only scenario that doesn't have two major airline pilots ignoring full scale deflection of their localizer and glide slope indications is that MAYBE they didn't select the Approach mode. After the first go around, they would typically re-select the ILS 4 approach in the FMC which would populate the points on their MFDs for situational awareness. They would be flying the pattern on autopilot and then need to select either the LOC and APP mode when they get that last vector and cleared for the approach. IF, and that's a BIG IF, they intercepted the FMC GPS final approach course but neglected to select the LOC and subsequently the APP mode (depending on how the approach clearance was issued), they would be flying the ILS 4 approach from the FMC GPS points (they would also have to be in LNAV and VNAV modes as well) instead of the localizer and glide slope. If they were task saturated and not seeing the underlying raw data, the command bars would look somewhat normal. But, that would mean they flew the ILS 4 based on GPS which may account for the ground track error. I'm guessing that they still had the ILS frequencies tuned but didn't get a GPWS "GLIDE SLOPE" aural warning because they stayed within GS limits as they drifted East due to GPS inaccuracies. The final "say reason for go around" (Sounds just like the Pilot Monitorings male voice) indicates significant task saturation.
I agree. This is totally feasible. Task saturation, removed from “normal” ops. The scenario you describe explains the near perfect offset of 1400’. Descending below minimums without runway in sight just compounded this mess. Technology is wonderful IF you use it properly.
At 9:15 I think you're right with your text on screen that it's not Southwest asking for the go around reasons (though the voice sounds similar). Tower replies as if it were someone else saying "This guy was not in line with the runway at all. He was like east of the final. He was not gonna land the runway."
SWA has a reputation for being fast on final but not sure if that was the case here. SWA also has the HUD installed which makes a hand flown ILS a lot easier than a Flight Director aided appch.
HUD on Captain’s side only on Non-max airplanes. Not sure about their Max’s since I didn’t get to ride on their jump seat as there were so few in the fleet when I retired in 2020.
My conjecture, F/O was PF, Capt PM. No HUD on F/O side so the F/O is relying on Primary Flight Display. All the majors have a lot of inexperienced crews right now with the retirements and COVID buyouts. As the Captain, you have to balance letting the F/O fly the approach in crappy conditions to gain experience and confidence and knowing or not knowing when it might be beyond their skill base. That inexperience level might be present in both seats. As for when to divert, my limit was two. If I had two shots at an approach and things didn’t improve, it was time to divert. Fate is telling you something.
@OfficialBlancoliriou Thanks Juan. Another thing that may of been an issue but it’s been a while so I might be off base. The B737 has an anomaly that’s called “Stand Off”. If you engage APPROACH with the autopilot on too soon it actually flys a parallel path to the LOC. If they missed the note that prohibits an autopilot flown approach and did this that would explain the path flown. This is why briefing an approach each and every time is so important.
Had several of these WS events on 4 ils flying BOS/LGA shuttle. Never had Loc bend at LGA 4 --however did have the 36 C ils cat 3 in CLT bend several times. Worst was 100kt tail wind on 4 R ILS BOS up to OM then 0 wind as reported by all preceding. flts. Smooth ride also in 75 with the good old RB211RR spooled and ready to TOGA.
She's just starting her shift and BAMMO HERE COMES A 737 wide and low and straight at her---datgummed straight she was rightfully excited with a full shot of Cortisol and Adrenaline to start her work day. Such stress hormones will challenge your "best language skills".
Juan, that was an excellent presentation. Your use of all that technology to explain the situation left a lot of questions for the NTSB to work with. As a former Navy GCA controller at an air station near Boston, I’ve dealt with these extreme right or left of course situations near the decision height call. At least I could see the course deviations on radar, although being so close to the landing threshold pilots did not always follow changes in heading commands. They are too busy looking for the runway. It seems like that may be the case here. How could they be so far off course? Were they flying the ILS for some of the approach then decided to take over manually and fly the ILS before they broke out of the soup? Very scary situation. I assume the captain was the voice of reason who suggested they divert. Thanks again Juan.
FLM stands for front line manager. Basically a Supervisor was manning the watch during the time of the incident. CIC is controller in charge and that is when a controller is acting in a supervisory capacity while an FLM/SUP is on a break or dependent on staffing.
@@revvyhevvy As Juan said, LGA is a very demanding environment, and from Newark, westbound trips to LAX or SFO, also demanding, at least were good layovers. The trips involving LGA generally weren't as productive and not worth the hassle. Watching the whales migrating north from the hotel at Cabo San Lucas in February was much more enjoyable.
Reminds me twice of doing an instrument approach in crappy visibility when we got visual the runway that was not where it was supposed to be. Quite a shock! First time it happened (at the same airport btw) went go around the second time we made a header for it once on visual and landed since we were super stable and had felt there was more than enough room to maneuver and line up after being somewhat, surprisingly, off centre.
Imagine showing up to take over your controller shift for the day and the very first thing you see is a huge aircraft that low to the ground and that far off course. Must have been all kinds of scary and confusing.
WOW! WOW! What a scary situation! Thank GOD for the eagle-eyed young lady Controller! Bless you, Juan, for bringing these Reports timely. I have been a pilot since age 30>>Never experienced ANYTHING quite this bizarre!
I'm not convinced the voice asking for reason for the 2 go arounds was the same voice as SW147 pilot, but certainly sounded the same. The first go around was the pilots call, so why would he ask "reason for go around" call that he himself made? And the lady ATC said "he" twice as if she wasn't talking directly to the pilot. Second, I don't think it ws a shift change for the ATC, I think she just jumped on freqentcy when she saw the airliner. The origial male voice tower controller was heard asking reason for go around for another flight.But all'n'all great catch for the lady controller. Nice Job!
The SW147 voice sounds identical to me. Maybe he misspoke or was high on something. It was an awfully weird question, since he _did_ declare the first go-around. It's all very strange. Was the PIC intoxicated? How do you deviate off the flight path so dramatically?
@@JBN137 After the second go around, I'm not sure it was the PNF becuase he asked "What was the reason for the two go arounds?" If it was the PNF, he would have been the one who called "go around" on the first one. Why would he ask the reason for "two go arouunds" if he is the one that called the first go around?
I doubt the ILS was faulty as many planes have landed safely prior to SW and even the planes coming in after SW, on short final, seemed to be perfectly aligned to the runway. Those 3D models are amazing! Excellent report.
Thanks for the summary Juan. Unfortunately I still have more questions than answers on this one, definitely an eye opening moment, just glad it didn’t end the way it could have.
My first air flight ever was in 1966, in a 727 out of Cincinnati to LGA. Sat in last row between the engines. Every sound seemed "wrong." Landing was over water until touchdown, at super high speed, since 27's had to land hot. Fairly terrifying first flight over all. All uphill from there.
Great stuff Juan, as usual. As someone who was born and raised in NYC, I should mention no one....and I do mean no one....ever refers to a highway in New York as a "freeway." The highway that skirts alongside LGA is the Grand Central Parkway (parkway translates to no trucks/trailers allowed).
What I don't understand is why the cockpit voice recorder has such a short time limit. With modern technology you could record a congressional debate on a device the size of an iPhone.
The tower told them to divert. and as to the anxiety level of the flight crew, that's only Juan's perception. But clearly flight after flight after flight were having EXTREME landing difficulty there. IMO they should have been on the edge of or outright closing the airfield. JB repeatedly said that conditions were terrible.
@@Bill_WooIn the video, the male pilot tells ATC they want to try the approach again (a third time), then he says wait a minute, then the female pilot comes on and says we'd like to divert.
If I recall correctly, FAA Controllers have a very elaborate radar tracking playback system in FALCON 3. Real time flight parameters with ATC to cockpit audio.
Their lateral path took them straight toward the LGA VOR which is located just southeast of the runway 22 threshhold. Could they have been hand flying in the wrong navigation mode (still on "direct LGA" on the primary display), wondered why there was no glideslope on the primary so used a backup display for that?
Interesting observation. Was trying to think how they could possibly be tracking to the VOR instead of localizer. Could only think of one, and it's a far stretch. They just did the ILS to 4 so frequencies, course and minimums would already be set and no reason to change them between approaches. 737 ILS approaches are flown in "approach" mode. Approach mode wouldn't work with a VOR frequency tuned. Can't imagine they'd be in LNAV/VNAV for any reason on a second ILS approach. Even if accidentally in LNAV/VNAV, the lateral path would be to the runway threshold and not the VOR. Unless reloading the FMS got royally messed up during vectors back. Kinda stumped on how this could happen. Far out scenario is one pilot had the VOR freq tuned in standby on their nav radio as a backup situational awareness tool (technique used by some pilots in the weather in case both FMS's crap out), after the first go around and hand off to approach control for another approach, accidentally toggled nav frequency from ILS to VOR instead of comm frequency, and never set it back because of task saturation. But if that were the case, the primary flight displays would be showing different indications if one pilot had ILS freq and the other had VOR freq. If they originally went missed for being unstable, they seem like the prudent type of crew to go missed for conflicting data on primary displays if VOR was accidentally tuned. But... why they didn't go missed at or below mins the second time is a big surprise. Definitely human factors going on. Hopefully the findings will be public one day, lot of questions about this one. Glad tower saw it and made the call.
Looking forward to the final report- this is bizarre, especially from SWA. The pilots union reps are being put to work on this one - at best, a "training opportunity/requirement", or if the FO is probationary/new, that pilot is toast, I predict. Flown into LGA a ton of times, never had an issue with alignment. ...though I messed up pretty damn good with both alignment and height once during a visual approach as a new FO on a beautiful day :) Juan might be right - Using autopilot, although prohibited by the approach plate? Also per Juan, they dropped below DH when the go-around order was commanded.
unlikey there will be any disciplinary action for either pilot. Sheesh. They did their ASAP reports, etc, no reason it would not be accepted by the gatekeeper, it was not an intentional or deliberate act.
@@skyboy1956 For their sake, hope you're correct. I know a probationary pilot who was not the pilot flying, but the aircraft had a no injuries incident flying out of LAX during climb out. Flash icing, stall, then inverted in IMC. Regional turbo-prop, so no Piccolo tubes/hot bleed air. Not yet under union protection, the union advised him to quit immediately, but the airline fired him one day after he resigned. Took 6 months to clear up, and keep his record clean.
The ATC audio is confusing. Which pilot was the captain? One would rightly assume that the captain would be flying in this mess, particularly at LGA, and the FO would be working the radio, which would make the female the captain, but the female doesn't sound very experienced on the radio, at least. Contrast Tammy Jo, who, while kinda sing-songy, was very clear, calm and affirmative in her radio patter (and a complete hero, of course -- just so impressed with her).
Female FP and captain flying the HUD. She is shaken and instead of her tellling the FO to tell ATC About diversion she just did it herself. Male voice is shaken FO/PM. ATC was the voice asking twice to two different flights the reason for the go around As per their requirements. Why were they off course? I’ve flown the shuttle and that approach about 3000 times17 years DC-9, A320. Never seen LOC deviation.
Thanks Juan. Good job. Lots of unanswered questions here. Some questions can not be asked nor even be considered if you get my drift. Been there done that. Good luck to all the new major airline Captains keep the blue side up.
This is a remarkably concerning incident. Thanks to Juan and the many knowledgeable commentators for their considered input to the discussion. I look forward to further analysis and official investigation report. I do fear and feel that the clock is ticking and the Swiss cheese holes will align again one day in US airspace on a busy commercial flight. I sincerely hope that I’m wrong. I commend the controller taking over the position, although no doubt she will take some flak for missing the appropriate call sign.
Perhaps the controller used a blind (no call sign) go around call because she didn't know which aircraft's nose gear was filling her tower cab window, and there was no time to inquire. I've heard the "GLIDESLOPE GLIDESLOPE" warning call out. Is there one for "LOCALIZER LOCALIZER"❓
There needs to be rapid action by FAA to push forward rulemaking on FDR/CVR upgrades to require 24 hours of data capture; AND supplemental rulemaking (because of the normal grandfathering of 1000s of units that will be exempt) that offers a less impactful software/hardware fix on current FDR/CVR units that permits 'bookmarking' a 30-minute window of data upon ATC command (accompanied by appropriate regulatory requirement for such command to be followed without exception). But FAA normally ignores the "free of fatality" red flags, preferring to wait until they have actual blood on their hands before initiating years of NTSB urging.
I was looking for this comment...worth the search. This incident along with the SFO/Air Canada Flt759 and Alaska Flt 1282 require FDR/CVR data preservation.
"Stand by......time to bust out the big mouse".... lol.... ...."breaking out of the weather...... and coming right at them...''....yup, that gives us a great visual of what the ATC was facing😳!! And with seconds to spare.....wow. "....what were the reasons for the 2 go around...?" I HOPE that was someone else! Great analysis as always....thanks, Juan! And even my dog knows, WHENEVER she hears your voice, she might as well find a good spot to sleep for the afternoon-- Mama"s probably heading down yet another aviation rabbit hole!✌🏽❤🔥 BUT! If she hears the Air Safety Institute guys, she knows THAT MEANS, we're heading out on a walk.......and she hangs out by the front door, taunting the cat that she gets to go to the park, lol. 😆
UPDATE!: 9:20 That was ANOTHER aircraft on the ground at LGA who wanted to know the reasons for the Go-Arounds so he could make a better Go/NO Go Decision. He elected to NOT GO until the weather (winds) improved. Windshear needs to be accurately PIREDed by Aircrews to help make informed decisions about the operation. Jb 4/7/24
I wish there was a PIREP broadcasting service on either ATIS or in a parallel channel so aircrews can get the latest update before a go/no go decision is made in dodgy weather.
Not a pilot, but I am a Radio Amateur. So apologies if this sounds like a stupid question: Was the aircraft possibly aligning itself with a sidelobe of the guidance beam? That could explain the deviations. Thanks.
Yes Juan, they pilots usually give a Windshear report after rollout. We have given one at LGA of 10-15kts. It can be tricky. Just the fact that Pireps are being given is enough to warn the pilots of the presence of Windshear as well as it being a positive or negative. Pireps are put on Wx sites and are relayed by ATC. It will be included in ATIS if the airport is reporting it. Winds can change a lot in a short period of time as in x-wind and an aircraft might be out of limits after lining up on the runway. A lack of situational awareness is going to be a factor here.
Female was flying thr approaches that's why. Pilot flying doesn't talk. After 2 failures and one of them being so massively pathetic it's ASTONISHING the pilot flying is even a fkn pilot much less airline pilot, the captain took over which is why the female was speaking on southwest after the second pathetic attempt
@@RWBHere I am wondering this myself.
Eagle Eye award for her! I’m glad the controller spotted this. This could’ve been tragic!
She could see but apparently the pilots were searching so hard for the runway they could not see what the plane was really doing.
The only problem was she panicked and DID NOT USE A CALL SIGN when attempting to issue a go around!!!
@@wturn5354 Was there time?
@@wturn5354I wonder if she wasn't the controller handling finals, and didn't even have them on a screen (for ID), but just saw them out the window?😮
Concerning that none of the bells and whistles went off!
@@dosgosyes, and not using a call sign frequently results in the pilot asking if that call was for them, or another pilot may ask as well and a LOT of time is wasted! There is a reason flights have call signs!
Some people owe a big thank you to the controller, she definitely saved the day and peoples lives, potentially including hers and the other controllers. What a way to start a shift, seeing a Boeing emerge from the mist heading straight towards your tower !
Amén 🙏🏽. Thanks to the air traffic controller. She saved many lives on that day.
As a retired controller, this is one of the most chilling events I've ever heard of. What a great save by that controller! Many many lives saved!
Sir
I would like to ask you a question. Do we have to many planes to Handel? Even if these pilots are the blame is it time to reduce the number of take offs and landings?
That controller deserves an award. She very likely saved hundreds of lives in that moment, possibly including her own. What a scary situation, and thank goodness for her quick and clear reaction.
That's why its a great job to have, rewarding in itself,, and why its so stressfull.stressful. Hopefully those bosses don't try and blame atc.
No, she didn’t even use a call sign, VERY POOR!
@@wturn5354 what, are you her superior???
@@wturn5354 She saved 100's of lives....give it a break!
@@wturn5354 🤦♂️ There’s always one if you, isn’t there? The time required to figure out and say their callsign might’ve been the difference between recovery and collision. The plane on terminal descent got the message and acted immediately.
You should watch this video again and listen to Juan’s detailed breakdown to understand how close they were to ending up in a ball of flames.
Always more enjoyable to hear Juan's analysis when there was no loss of life.
Absolutely!
I absolutely agree. Same with Mentour Pilot!
ASDE stands for Airport Surface Detection Equipment....or at least it did 12 years ago when I retired. I am pretty sure that the "new" controller was receiving a change of controller briefing from the "old" controller when she saw that Southwest was not where they should have been so she took appropriate action. Well done!
I would be interested to learn how controller-to-controller briefings occur at an area as demanding and critical as this is. How do you hand off such busy airspace without reducing your situational awareness? Is there an overlapping handoff, where controller taking over just observes for 30 mins or something so you can minimize the words that need to be spoken off air?
I agree this controller saved the day. A lot more is needed to determine what happened in the airplane.
Indeed.
Well done.
@@seanur2414 The relieving controller observes for several minutes then will say “I got it”, then the controller that was relieved will stay for several minutes after to ensure integrity.
Thank goodness that controller looked out the window. I suspect that when starting a shift there's a lot to review on the computer screen to understand where everyone is at. That could have been a major disaster destined for a movie script.
...and people want to remove humans from these systems. The human is the one thing that saved the day!
Precisely!
I mean…
Same can be said about machines. I would argue that machines helped with more landings than they hurt however I'm not at all suggesting removing humans.
@@Kayak51if it ain’t broke don’t fix it
@@alexanderwalley2639 Depends on what you define as "broke"
FALCON is a radar replay tool that we controllers have. It's like having Victor put a video together for us except that it's much quicker, has more detail in several ways, but it doesn't come with subtitles. We controllers use FALCON to do radar replays somewhat regularly. Sorry that we FAA people speak in acronyms like a second language. (Though I am current FAA, my views and opinions are expressed in a private capacity).
No one knows who you are bozo, no need for a disclaimer
Brand new GA pilot here after happily retiring early from Pfizer, so bear with me. Do Southwest 737s have Cat III autoland capabilities in their aircraft? Any ideas why the La Guardia plates say "Autopilot coupled approach not authorized for Runway 04"? Any ideas what Southwest's minimum are?
@@PfizerRN_NavyReserveCaptain Juan explains it in the video. First of all, no autoland on Rwy 4. Best rumour is that the localizer is known to get squirrly near the ground and would cause too much movement of a coupled aircraft.
@@williamcandee5267 Appreciate it
@@PfizerRN_NavyReserveCaptain LGA is known to have problems with magnetic compass interference due to how it was built, using fill from Rikers over steel-frame pilings. I don't know if ILS anomalies are also connected to this problem.
I’ve landed probably 180 times of in LGA, in good and bad weather, minimum visibility, windy, rainy and very snowy-in Barons, bonanzas, DC9’s, MD80’s, 727’s and 757’s and 767’s. It’s a very demanding airport, vfr and especially ifr-then add snow! Most airline pilots are intimidated before they even get close to the airport. The secret is to know your airplane, always be at the appropriate speed, land in the first 1000’ and don’t float in the flare. If you can do ALL that, you are not intimidated! Glad I’m retired, and don’t have to endure that any longer🤪
There needs to be some good mentor programs for the new gen's, maybe even write some pamphlets or make some training material/videos?
I would only land at LGA if they paid me double.
If you fly your plane properly it’s really a piece of cake.
767 impressive
If that is truly a “secret” it’s time to inform all pilots!
The consequences of not being aware of this secret could potentially be the difference of success or failure🙏
Juan, I think it's a true testament to the quality of your reporting that tower controllers are not only here watching your videos but also willing to stick out their necks to comment.
Also FAA guys
The controller who called for the go-around sounded like they were watching the plane bear down on them and didn't like the view.
She did a awesome job
I'll wager the oncoming controller was standing right there at the controller spot she was taking long enough to witness the first go-around and was looking out the cab window for the aircraft when it descended below the cloud layer. Standing in the background observing gives one the time and perspective to sense these types of things in all situations in life.
Well said.
Could very well be. It is a great save. Controllers are regularly reminded that during and immediately after Position Relief Briefings (PRBs) the risk of a mistake or oversight is much higher and we are trained to be even more vigilant because of it. During PRBs there is a lot of information being exchanged verbally, while traffic continues to move, and it takes careful focus to stay on top of things.
JetBlue immediately made the right call on the Low Alt alert from the tower, don't try to fix it just go around, very prudent. There's no harm, no foul on a decision to go around.
Shouldn't they have received in the tower an altitude alert for SW too, similar to the one received for JetBlue?
I doubt the system is designed to detect aircraft that are not lined up with the runway.
@@42dunbar The system is designed to prevent terrain collisions for other aircrafts too, not just for the ones on the approach.
They almost wiped out a neighborhood in Queens! Looking at the ADS-B for 17:01:28Z, they were at 275 feet pressure altitude and STILL DESCENDING at 576 feet per minute! KLGA altimeter was 29.79, so that means they were at 135 feet MSL. Street level there is 27 feet MSL, so they were 108 feet above street level and maybe 75 feet above roof level! Well, at least their static port was! I wonder how far below the static port their wheels were? If they had delayed the go-around for a few more seconds...😮
Good call about the equipment being that high.😅
But you have to measure it from the "sensor," which could be higher or lower inside the aircraft than the actual static port.
@@johnhill2927 Ah, good point about the location of the actual pressure sensor. I also downloaded the EGM96 corrected GPS kml file from ADS-B. It shows a minimum altitude of 47 meters, or basically 154 feet MSL. I suppose GPS altitude is not exactly the same as antenna height? Is there some additional error because the velocity factor of the GPS antenna cable is less than 1? Or is the GPS solution made right at the antenna by embedded electronics?
In these days with cameras EVERYWHERE, it is highly likely there is some ground based video of this out there. I'm surprised we haven't seen any yet.
@@Highside713 People in Queens are so used to low flying planes that this may not have registered, so they didn't review their security cams/doorbell cams.
Very strange they did not go around by themselves
And Lloyd Bridges freaked out and dove out a window when he saw the airliner heading straight for him!
Guess he picked the wrong week to quit sniffing glue.
He's comin' right at us!
Shirley not!
@@danielayersdon't call me Shirley
😂😂😂😂😂
MOR is the actual report name-“Mandatory Occurrence Report”, and the FLM is the ATC Front Line Manager-the Sup.
A PRB is a position relief briefing-the exchange/briefing that happens when a new controller takes over a position from the one leaving.
Do you think it's possible they shut off alarm for the previous flight (low altitude) and somehow cancelled the new alarm that should have gone off?
@@caroltlw Local control (tower) is nearly all visual-primary responsibility is runways. There is likely radar available to the LGA tower controllers, but it’s for situational awareness, not radar services. That tower is so busy, it’s not likely they would have time to issue low altitude alerts based on that. If they got one, they would look out the window and verify before saying anything-just like what this controller did. I’m not aware that any alarms like that can be “turned off”. ATC is a very “CYA” activity. The default would be to warn/notify a pilot if there was any concern, rather than to mute anything that could end up biting you in the rear end.
@@theflyingbisq
OK, I was confused by the reference in the report to the ADSE/ATAP alert not going off and being investigated. I thought maybe that was something in the tower. Maybe "reset" is a better word for what I was thinking... flashing lights or something.
Thanks for the insight, Bisq
@@caroltlwit’s a good question. It may have been so far east of the taxiway that ATAP didn’t make a prediction that the inbound was lined up with the taxiway. I’m not that familiar with the technical aspects of it. It’s only available at like 40 facilities.
By the time the controller got out the words SWetc, which takes about three seconds, the plane would be about 600 feet closer. Sticking to your formality in this case could have killed everybody on board and more on the ground.
When you see a brick falling on someones head, Do you say” Hey over there, A brick is falling on you” or do you scream watch out. It doesn’t matter if everyone has a look. There’s a time for formality and a time for commonsense.
You don’t get consultation times in such an event. Lucky the Controller just gave ashout out instead of giving a formal call sigm.
Indeed, exactly.
MOR is the mandatory occurrence report and the FLM is the Front Line Manager. 16:42
Amazing that the airplane was at 100 feet above the ground so far off course. Good job by the ATC controller taking immediate action during a shift change.
Hey at least the glideslope was working. If they been on course that would have put them right in the touchdown zone of Rwy 04.
But if you’re breaking out of the soup at 5-600’, how do you get down to 100’ without noticing what is wrong? Descending at 500’/min, going from 500’ to 100’, that should easily be 30+ seconds in the clear, even accounting for any loss of altitude while spooling engines up.
Female was flying thr approaches that's why. Pilot flying doesn't talk. After 2 failures and one of them being so massively pathetic it's ASTONISHING the pilot flying is even a fkn pilot much less airline pilot, the captain took over which is why the female was speaking on southwest after the second pathetic attempt
Retired airline Captain, I have flown many many times into KLGA. Juan, please note that the ILS Hold Short line on Taxiway Bravo for ILS 4 is not at the runway threshold. It is well short of where ILS Hold Short lines are normally located for most runways. This makes me wonder about the the deviations and the number of Go-Arounds. It may be that there was airplane or vehicular traffic encroaching past the ILS Hold Short marker.
Nobody taking off rwy 4...
Hmmm... That's a very good possibility.
Weren't they using Rwy 13 for Departures?
I think he said in the video that there is no indications of someone in the ILS critical area…but maybe that isn’t official yet
Duly noted, and thank you!
You know it's a bad day when you end up on Blancolirio.
If you are still alive
The reason for the uncoupled approach with no AP on ILS 04 is because of the interference of the rwy 13 system or building at the intersection of rwy 13. I see VASA had the answer. I've flown the ILS 04 into LGA at mins, but the wx was not as windy although have flown into LGA when the wind was bad which is often. Disengaging the autopilot as soon as you intercept the LOC is pretty straight forward flying even if this is mins wx. That's our job! If your in an uncontrolled approach then you initiate a go-around. If you miss twice and wx is really bad you divert to your alternate. This is all textbook stuff. After your 2nd approach your probably at BINGO fuel anyway, so off to ALT, notify ATC and Company and get the heck out of it. Windshear is not fun at low altitude.
Not too sure why SW was so far off track on the LOC. Did they intercept the false reading? ILS instrument equipment faulty? You intercept the LOC within 10 degrees of centreline 18nm out. Not a false Glideslope as they seemed to be at right height upon breakout. But that far off runway to the right is got to be at least a dot out? Glad to see they diverted and landed safely in PHL. I think they have some questions to answer. Why that far off centreline and not know it?
Any chance they could have been picking up the wrong freq - like for a different nav beacon or something?
Based on other accidents I wonder if there were 4 eyes looking for the airport instead of 2. Seems like the stress and workload after a miss might have contributed to a loss of situational awareness.
"Looks like I picked the wrong week to quit sniffin' glue..." 🙃🙃🙃🙃
"He's coming right at us!! Ahhhhhh!!" 🤣🤣🤣🤣🤣🤣
It’s like a disaster movie!
@@kendrapratt2098 More like a comedy movie. Look up Lloyd Bridges in the movie Airplane...
Or quit the magic mushrooms.
Joey,have you ever seen a grown man naked?
Surely you can’t be serious 🧐
I was a controller in the old LGA tower, which was much closer to the runways than the current tower. I remember at least a couple times when we were scared that a missed approach/go around might hit the tower!
“If I can land it there, I’ll land it anywhere…”🍎
Sinatra got his inspiration from his brief ATP career….
Underrated 🍎💕
Blancolirio is far and away the best aviation crash/incident commentary on UA-cam. Thank you Captain Browne for keeping it real.
He really is. Very black and white.
Crash videos ?
The gold standard
People need to stop making Juan have to do these reports.... 😢
YEP!…..👍👍
Stop voting for the same stupid people who neglect their post.
Agreed. (But we would all miss him so much!)
When pigs fly
No one is making Juan Brown do anything. He's a man's man.
that controller was that called out the go around is a hero for noticing and acting on it. that jet was definitely crashing into the houses before the airport
Nonsense! The crew was probably already taking corrective action since they had broken under IMC and probably were quite shocked to see the tower ahead.
She was paying attention. Thank god
That lady ATC was very firm in her call and a hero, pilot unable to explain his huge near miss and near crash. I think that pilot will be driving Taxis in NY from here on.
Driving a taxi in Manhattan would be more difficult and more stressful than landing at LaGuardia...maybe he could be an engineer's mate on MV Dali...erp...quality control at Boeing?
Let's wait for NTSB. There is a possibility of equipment failure (glideslope).
She definitely saved the day! I imagine how I would have been shaking after an incident like that. So great it worked out good and everyone could walk away harmless with the new things to learn!
A whole flight crew and tower as soon as they realised what nearly happened.
This was so incredibly close to being a major accident. If that new controller wasn't so aware, assertive and transmitting a very clear no nonsense instruction, a few seconds later we would be talking about hundreds dead. There was 5 seconds at most in that becoming global news.
Wonder how many other planes in the area pulled up at her command. Never said who she was or who she was talking to. And she did a great job. Probably saved many lives. Tell her to take a deep breath. In only 8 hours and 59 minutes, counting lunch, she can call it a day.
Approach frequently. Expediancy trumps, there was 1 second to communicate with.
Her performance was POOR, panicked and didn’t use a call sign!
So what! The first thing she saw after setting her coffee down was a 737 headed for the her IN THE TOWER!!!
@@wturn5354Are you sitting in an armchair?
As a retired SWA 73 capt. Hand flown ILS to mins would be a HUD flown ILS. So how can the crew be that far displaced? Twice? Sure the WX was a factor, judging by the number of go arounds. Hopefully the capt pulled the recorder CB.
AFS Guidance Engineer here.. this looks like a typical case of LOC deviation beyond 1 dot.. The fact that the chart published AP use not authorized, and the fact the flight crew did not see this deviation on the ND, points us to believe that there was some sort of interference in the LOC signals. Meaning AP was most probably ON and the aircraft was correctly "tracking" the LOC signals, however this LOC signal was itself "bad or incorrect", but neither the AP computer nor the pilots know this. This interference (deviation is LOC signals) can be due to poor shielding of the LOC antennae (at the end of the RWY 04) due to ground operations (aircraft taxiing in front of the antenna). LGA is located in a very dense (EM radio signals) area with TEB and JFK in close proximity, which could be prone to frequent signal interferences especially in case of enhanced LOC capture approaches.
I was once analysing an incident report from Qatar Airways captain flying in approach to DOH RWY 34R, and the aircraft was targeting (nose alligned) straight to the Banana Island and clearly deviating from runway 34R centerline.
Why is the ILS to 22 and 13 not affected by JFK and TEB? EWR is also an airport that exists in that area.
This is digital transmission of 1's and 0's you are talking about? It's different information if the antenna is in a different position? What?
@@FamiliarAnomaly Who said anything about it being digital? If you're not aware of how ILS works, maybe google "How does ILS work". Wikipedia has a good article on it. Not sure why you're assuming it's digital?
@@FamiliarAnomaly The localizer is an array of antennae that all transmit on slightly different frequencies, and the plane triangulates from them. If one or more of them are blocked by another plane, garbage, trucks, or even too much snow, then the triangulation can be wrong and distort the inferred geometry. The system uses the relative strength of each signal, not some coded message in 1s and 0s. So if a plane was taxiing too close, it could have sent that landing plane off in a veering direction but not any other plane that day. Also because other planes were following the rules and not using auto pilot.
This has happened before. I lived off the end of rwy 4 in Jackson Heights for 7 years. Normally aircraft would approach diagonally behind my building a several blocks to the west. However one evening back about 2010-2011 in similarly bad weather an aircraft came right over my building a lot lower than it should have. Then it happened 2 more times in a row. Looking at Juan's screen at 12:33 brought me right back as that would have been the same flight path as that night. Scared me enough where I wanted to call the Port Authority to report it but after the third aircraft I think they changed runways to 22. I also do not recall if the new tower was live yet. Thanks for the report.
I was out walking in that rain, right under the approach path that day in Brooklyn. Seeing the planes popping out of (and back in to) the clouds was cool! I may have even seen this flight, definitely saw some SW planes.
That had to 'trippy'!
Once again Juan, thanks for explaining things where us "non-pilots" can understand, you ROCK!
The “Falcon” reference is to an FAA analysis system called “Falcon View” which allows for playback of recorded radar and voice data.
I once flew an ILS where the signal identified and it came in, but it was waaaaaay off. Having plates live as a gps reference was invaluable as you could see it tracking way left. Turned out, someone had hit the glide slip with a mower shortly before and threw it off. Pretty wild that we don’t have redundancy for ILS. At this point, we should have gps backed up reference systems to see redundancy early and continuously in the approach!
I think that call for the reason for the two go around was an internal coordination communication between local control and the approach control. That being said LGA can be tricky in that type of weather. All sorts of wind shear and you get rotor off of the buildings which can make for a rough day. The reason that the autopilot isn’t authorized is because there are two very busy roadways very close to the approach end of the runway. The Grand Central Parkway and inside the airport perimeter, the airport service road which is not controlled by ATC and particularly when any large vehicle crosses the extended center line on the service road the localizer will windshield wiper. Sometimes it can be very subtle and not easily detectable by the flight crew. After some 30 years of going in and out of there I’ve seen it all including many times having the loc needle bang from side to side which of course initiated a go around. The perimeter roadway is just beyond the ILS critical area and crosses the approach end of the runway.
Been looking forward to this report. Thanks for getting on it.
Why, did you know something beforehand?
@@GardenGuy1942 VASAviation posted this on Mar 25, two days after the incident occurred, and his ADS-B analysis the next day. Been waiting for a write-up on any investigation into this.
@@xplayman I see. I ask because I don’t cause plane crashes. Thank you.
Best,
Dean
I did a lot of approaches into LGA and ILS #4 always made me nervous especially when it was foggy and raining Good Report Juan.
PRB- Position Relief Briefing. That’s why the voice changed. A new controller had just taken the position.
Probably hadn't sat down yet, likely had just walked in, saw something that shouldn't be happening, grabbed the approach mike & yelled.
@@christibritton1436probably didn't even know the flight, just needed to alert anybody & everybody
Thank you Juan for reporting on this, and indeed all of your aviation safety reports! And I also want to acknowledge the pilots in this report, all of them. They all responded correctly too! Not only the Southwest pilots, but also the other pilots who went around, and the other controllers too. This was just a very nasty time to be flying into LGA.
The Southwest pilots messed up big time. No other plane got 10 degrees off the localizer and 150 feet below minimums.
@@igclapp This should be a learning experience if the process works correctly.
@@james_chatman This was apparently some type of CRM failure. The PM was not monitoring properly. Hopefully they'll find out why and it will be a lesson learned to avoid a future recurrence.
Possible explanation. Upon breaking out below the ceiling at about 600 feet, the pilot visually transitioned to what they thought was the runway. The transition from instruments to a visual
on the runway is a critical phase, especially with reduced visibility as was the situation here. “Rabbit” lights, VASI/PAPI, and a quick peak at the ILS deviation bars can help avoid biting off on something that looks like a runway but isn’t (a taxiway, car lights, a roadway, etc.)
I was base at La Garbage back in the 80 with Eastern. Low visibility approaches were always a bitch because of turbulence, aircraft spacing Ney York traffic congestion. It has changed very little in the last 35 years. Not enough runways, too short runways and the added pressure of the whole situation. At least they took down the sky jump at the end of the runway into Flushing Bay.
Ahh, VasAviation and Blancolirio, like fine salmon and white wine! Just perfect together!
Even better some wild copper river salmon with a nice Pacific NW Pinot Noir...
Yep, I had caught Victor's (Vasaviation) post hours before! He was ON IT immediately!!
Fully expected Juan to chime in, unless he was over the Pacific somewhere!!
Add some MentourPilot to that and it's the trifecta.
100%
More like beer and a kebab IMO!😂😂
Outstanding video and explanation. I've been a passenger flying into 4 at LGA, it felt like we were going to hit a building! I can't imagine how frightening it would be to miss that bad.
Your video was clear and concise. I am very interested to learn more.
I live on Long Island and it was monsoon season on the day this occurred. I'm glad they made it to Philadelphia without further incidents. Thanks for your breakdown Juan. You and Victor are a great team 👍🏻
They first said PHL but then corrected that they wanted to go to PIT, their first alternate. It is about 4:40 in VASAviation video.
Victor from VASAviation did a follow up where he showed that the reason for the prohibitive on autopilot coupling is due to a hotel that was built that interferes with the localizer
not sure that's the issue...
@@blancolirio Sounds like a case of flying with the autopilot on a little too much.
That sounds suspicious, I’m not a pilot at all but you’d think they’d take that into consideration before building a hotel that could interfere with landing. Lol
@@daveg-Vancouver_Islandthe hotel was probably already there
Every directional antenna has a lobe. Also, RF ducking/reflection for the geography (body of water, building roof/wall materials).
During my prior life performing tech ops in commercial broadcasting, I read some of the trade publications. There was an article on ducting, when a body of water causes undesired multipath reflection (false echoes). Another article on tower service maintenance personnel safety, where FM stations operating in the lowest FM frequencies must significantly decrease transmitter power to avoid cooking balls, whereas those in the 100's seemed to be a lesser personnel safety issue as the energy instead reflects. Horizontal ILS transmits at 108 to 112 MHz. So, now I am wondering if something temporarily blocked the directional ILS ground transmitters' antenna array, causing the aircraft ILS receiver to lock onto a lobe that reflects off the tower or water, coupled with not looking out the windshield (or nose cone visually blocking due to AoA).
Notice that after the second go around, different voice on the radio. Sounds like the PF and PM switched places. Perhaps the Captain took the controls. Just speculating.
yes, what I am thinking
Exactly my
Thought also
I believe the female voice was the captain who made the decision to divert.
@@billmoran3812She was pilot flying though for both approaches.
Diversity hiring.. that’s the real story here. How long before people die?
11:46
With regard to the localizer getting wavy for the 04 approach, I think I can see the reason. Runway Drive passes directly in front of the right side of the localizer antenna array at the foot of the runway. The Q48 bus, and some airport shuttle buses and other tall broad sided vehicles pass directly in front of the line of sight of the localizer antenna.
That's probably why the localizer antenna gets all "screwy" and you can't fly that approach autopilot coupled.
Actually, Runway Drive passes directly in front of the runway 22 localizer array. The runway 4 localizer array is located at the NE side of the runway, on the water.
You could hear the near panic voice of the tower controller, she saw a lot of jet in the window. Wow.
She did her job.
LGA TWR dialogue at 9:34 sounds to me like "This guy was not aligned...He was, like, east of the final." It sounds like they were talking to a third party.
Or still in the midst of a shift or position turnover
I assumed that was an internal ATC communication. Did that go out on frequency?
I think the center was asking the tower why there were two go arounds and tower responded that the plane was misaligned. Odd that it was picked up with other transmissions.
Bit like a stuck mic problem.
@@beenaplumber8379I think so
That controller needs to be recognized for her immediate and clear action.
She prevented absolute certain carnage!
Clearly, there are some definite shortcomings with critical equipment at that facility. Maybe this incident forces the necessary changes.
I hope that controller was recognized for that go around. She saved hundreds of lives! That was seconds from a huge disaster.
I’d bet they had already initiated the go-around before the controller said anything.
@@gregg3138 they clearly didn’t…
It's what air traffic controllers get paid to do.... To prevent exactly this sort of thing from happening.
We don't need to give "atta-girls" and "atta-boys" to people who are just doing their job. 🤷♂️
@@straybullitt you leave your shopping cart in the middle of the parking lot, don’t you.
@MrHimynameisdanny
I actually NEVER do that, Danny.
I just don't see the need to give accolades to public servants who we pay to sit on their asses most of the time, and then do a job when we need them to do it. It was all right there in the job description when they were hired.
The sense of entitlement that people have nowadays is incredible.
PRB - Position Relief Briefing. A new controller was taking over the position, and the (required, and recorded) relief briefing took place from the controller being relieved to the oncoming controller
Ive done that approach for 30 plus years, and yes you do get loc scaling on the ILS 4. Its caused by a road near the loc antenna, that when trucks pass the antenna you get the scaling. The SW 737 most likly had the auto pilot on.
So, the ILS approach, which is certified as a precision approach, is anything but precision. One would wonder how this approach could be published when it is subject to anomalous behavior..
Yup its been like that for as long as I can remember. Thats why its call LaGabage.
@@donallan6396 This is an autopilot limitation which the approach plate specifically states that "AUTOPILOT COUPLED APPROACH NOT AUTHORIZED". Whether or not you are using an autopilot has nothing to do with the precision of the approach. Some autopilots can have high gain when trying to track a localizer or glideslope signal which, if disturbed and very quickly goes full scale, the AP might aggressively maneuver the aircraft in an undesired state in order to catch it. These approaches are flown, tested, and retested by FAA "Flight Check" aircraft in order to maintain the integrity of instrument approaches.
Third world airport. Have never come across a large airport with that kind of limitation.
@@ACPilot Columbus, Pittsburgh, Miami, Monterey....
Wow, this is quite distressing. I wonder since they were so far off course and so low, and if Autopilot was not on, would there be "pull up" or "terrain" warnings? At 100 ft, they were not only in danger of hitting the tower, they were right over homes or offices and risking barreling into those as well. That other ATC person really did save the day. Thanks, Juan, for the overview. I'm looking forward to more info when available.
Permission to buzz the tower?
Negative Ghost Rider, the pattern is full!
Oh my goodness HA !!!
Negative Maverick. My pants are full.
😂
Cleared to buzz !
FLM- Front Line Manager. Just the ATC supervisor on duty.
Juan, thank you for explaining this incident and making it easy to understand , for a non-pilot aircraft enthusiast such as myself, as to exactly what happened .....great channel !!!
Sounds like the controller needs to get a shout out for being alert.
Just guessing here, but the only scenario that doesn't have two major airline pilots ignoring full scale deflection of their localizer and glide slope indications is that MAYBE they didn't select the Approach mode. After the first go around, they would typically re-select the ILS 4 approach in the FMC which would populate the points on their MFDs for situational awareness. They would be flying the pattern on autopilot and then need to select either the LOC and APP mode when they get that last vector and cleared for the approach. IF, and that's a BIG IF, they intercepted the FMC GPS final approach course but neglected to select the LOC and subsequently the APP mode (depending on how the approach clearance was issued), they would be flying the ILS 4 approach from the FMC GPS points (they would also have to be in LNAV and VNAV modes as well) instead of the localizer and glide slope. If they were task saturated and not seeing the underlying raw data, the command bars would look somewhat normal. But, that would mean they flew the ILS 4 based on GPS which may account for the ground track error. I'm guessing that they still had the ILS frequencies tuned but didn't get a GPWS "GLIDE SLOPE" aural warning because they stayed within GS limits as they drifted East due to GPS inaccuracies. The final "say reason for go around" (Sounds just like the Pilot Monitorings male voice) indicates significant task saturation.
I agree. This is totally feasible. Task saturation, removed from “normal” ops. The scenario you describe explains the near perfect offset of 1400’. Descending below minimums without runway in sight just compounded this mess. Technology is wonderful IF you use it properly.
At 9:15 I think you're right with your text on screen that it's not Southwest asking for the go around reasons (though the voice sounds similar). Tower replies as if it were someone else saying "This guy was not in line with the runway at all. He was like east of the final. He was not gonna land the runway."
SWA has a reputation for being fast on final but not sure if that was the case here. SWA also has the HUD installed which makes a hand flown ILS a lot easier than a Flight Director aided appch.
HUD good point.
HUD on Captain’s side only on Non-max airplanes. Not sure about their Max’s since I didn’t get to ride on their jump seat as there were so few in the fleet when I retired in 2020.
My conjecture, F/O was PF, Capt PM. No HUD on F/O side so the F/O is relying on Primary Flight Display. All the majors have a lot of inexperienced crews right now with the retirements and COVID buyouts. As the Captain, you have to balance letting the F/O fly the approach in crappy conditions to gain experience and confidence and knowing or not knowing when it might be beyond their skill base. That inexperience level might be present in both seats. As for when to divert, my limit was two. If I had two shots at an approach and things didn’t improve, it was time to divert. Fate is telling you something.
@@carygrant8796Best comment on this thread ! Totally agree
@OfficialBlancoliriou Thanks Juan. Another thing that may of been an issue but it’s been a while so I might be off base. The B737 has an anomaly that’s called “Stand Off”. If you engage APPROACH with the autopilot on too soon it actually flys a parallel path to the LOC. If they missed the note that prohibits an autopilot flown approach and did this that would explain the path flown. This is why briefing an approach each and every time is so important.
Had several of these WS events on 4 ils flying BOS/LGA shuttle. Never had Loc bend at LGA 4 --however did have the 36 C ils cat 3 in CLT bend several times. Worst was 100kt tail wind on 4 R ILS BOS up to OM then 0 wind as reported by all preceding. flts. Smooth ride also in 75 with the good old RB211RR spooled and ready to TOGA.
Fascinating. Thanks for this, Juan. Flying has become so common that it’s easy for us backseaters to forget how really complicated it actually is.
7:50 "you were like - not on the approach" you can tell she was SHOOK
She's just starting her shift and BAMMO HERE COMES A 737 wide and low and straight at her---datgummed straight she was rightfully excited with a full shot of Cortisol and Adrenaline to start her work day. Such stress hormones will challenge your "best language skills".
I spent 4 months on that island just past the end of runway 04. Glad to have that part of my life behind me.
Rikers I presume
@@landshark7154 Yes sir.
Don't do the crime if you can't do the time ! !
Juan, that was an excellent presentation. Your use of all that technology to explain the situation left a lot of questions for the NTSB to work with. As a former Navy GCA controller at an air station near Boston, I’ve dealt with these extreme right or left of course situations near the decision height call. At least I could see the course deviations on radar, although being so close to the landing threshold pilots did not always follow changes in heading commands. They are too busy looking for the runway. It seems like that may be the case here. How could they be so far off course? Were they flying the ILS for some of the approach then decided to take over manually and fly the ILS before they broke out of the soup? Very scary situation. I assume the captain was the voice of reason who suggested they divert. Thanks again Juan.
Wow!.....it's so good to hear that a real pair of eyes averted an absolute catastrophe!....
Box 4 "Significant Occurrence?" is marked "No". I know it's just paperwork, but a near catastrophe deserves a "Yes" so that it can be taken seriously.
FLM stands for front line manager. Basically a Supervisor was manning the watch during the time of the incident. CIC is controller in charge and that is when a controller is acting in a supervisory capacity while an FLM/SUP is on a break or dependent on staffing.
When I flew out of EWR , I specifically would bid to avoid any pairing that went into LGA at all. Cabo trips were my first bid...
Why would that be???
@@revvyhevvy As Juan said, LGA is a very demanding environment, and from Newark, westbound trips to LAX or SFO, also demanding, at least were good layovers. The trips involving LGA generally weren't as productive and not worth the hassle. Watching the whales migrating north from the hotel at Cabo San Lucas in February was much more enjoyable.
Reminds me twice of doing an instrument approach in crappy visibility when we got visual the runway that was not where it was supposed to be. Quite a shock! First time it happened (at the same airport btw) went go around the second time we made a header for it once on visual and landed since we were super stable and had felt there was more than enough room to maneuver and line up after being somewhat, surprisingly, off centre.
Is it possible the PF mistook the tower for the runway through the rain and thought they had visual?
I'm pretty sure the runway was exactly where it was supposed to be ✈️🛬 you on the other hand ... Lol
I've been waiting for this one. Good job as always Cap. !
Did you cause this?
@OfficialBlancolirio8 do you want my credit card information?
Imagine showing up to take over your controller shift for the day and the very first thing you see is a huge aircraft that low to the ground and that far off course. Must have been all kinds of scary and confusing.
That's usually how my Mondays start out.
WOW! WOW! What a scary situation! Thank GOD for the eagle-eyed young lady Controller! Bless you, Juan, for bringing these Reports timely. I have been a pilot since age 30>>Never experienced ANYTHING quite this bizarre!
I'm not convinced the voice asking for reason for the 2 go arounds was the same voice as SW147 pilot, but certainly sounded the same. The first go around was the pilots call, so why would he ask "reason for go around" call that he himself made? And the lady ATC said "he" twice as if she wasn't talking directly to the pilot. Second, I don't think it ws a shift change for the ATC, I think she just jumped on freqentcy when she saw the airliner. The origial male voice tower controller was heard asking reason for go around for another flight.But all'n'all great catch for the lady controller. Nice Job!
Yes she must be rewarded. But it should never come to 1 piece of swiss cheese in the first place. System fail.
PRB in the summary is Position Relief Briefing. The second controller was the one who just took over the position.
The second 'go around' was called by the controller, after which the PNF asked "why?" "Duh. Because you were about to crash (into us)," she replied.
The SW147 voice sounds identical to me. Maybe he misspoke or was high on something. It was an awfully weird question, since he _did_ declare the first go-around. It's all very strange. Was the PIC intoxicated? How do you deviate off the flight path so dramatically?
@@JBN137 After the second go around, I'm not sure it was the PNF becuase he asked "What was the reason for the two go arounds?" If it was the PNF, he would have been the one who called "go around" on the first one. Why would he ask the reason for "two go arouunds" if he is the one that called the first go around?
I doubt the ILS was faulty as many planes have landed safely prior to SW and even the planes coming in after SW, on short final, seemed to be perfectly aligned to the runway.
Those 3D models are amazing!
Excellent report.
On top of that, SW was well aligned during their first approach
@@Raoul_Volfoni On the taxiway?
Thanks for the summary Juan. Unfortunately I still have more questions than answers on this one, definitely an eye opening moment, just glad it didn’t end the way it could have.
My first air flight ever was in 1966, in a 727 out of Cincinnati to LGA. Sat in last row between the engines. Every sound seemed "wrong." Landing was over water until touchdown, at super high speed, since 27's had to land hot. Fairly terrifying first flight over all. All uphill from there.
Great stuff Juan, as usual. As someone who was born and raised in NYC, I should mention no one....and I do mean no one....ever refers to a highway in New York as a "freeway." The highway that skirts alongside LGA is the Grand Central Parkway (parkway translates to no trucks/trailers allowed).
What I don't understand is why the cockpit voice recorder has such a short time limit. With modern technology you could record a congressional debate on a device the size of an iPhone.
"We'd like to divert - we are too embarrassed to land here."
Can’t blame them
They were not the only flight that had to abort.
We’d like to divert long enough to over write the CVR
The tower told them to divert. and as to the anxiety level of the flight crew, that's only Juan's perception.
But clearly flight after flight after flight were having EXTREME landing difficulty there. IMO they should have been on the edge of or outright closing the airfield. JB repeatedly said that conditions were terrible.
@@Bill_WooIn the video, the male pilot tells ATC they want to try the approach again (a third time), then he says wait a minute, then the female pilot comes on and says we'd like to divert.
If I recall correctly, FAA Controllers have a very elaborate radar tracking playback system in FALCON 3. Real time flight parameters with ATC to cockpit audio.
Their lateral path took them straight toward the LGA VOR which is located just southeast of the runway 22 threshhold. Could they have been hand flying in the wrong navigation mode (still on "direct LGA" on the primary display), wondered why there was no glideslope on the primary so used a backup display for that?
Interesting observation. Was trying to think how they could possibly be tracking to the VOR instead of localizer. Could only think of one, and it's a far stretch. They just did the ILS to 4 so frequencies, course and minimums would already be set and no reason to change them between approaches. 737 ILS approaches are flown in "approach" mode. Approach mode wouldn't work with a VOR frequency tuned. Can't imagine they'd be in LNAV/VNAV for any reason on a second ILS approach. Even if accidentally in LNAV/VNAV, the lateral path would be to the runway threshold and not the VOR. Unless reloading the FMS got royally messed up during vectors back. Kinda stumped on how this could happen. Far out scenario is one pilot had the VOR freq tuned in standby on their nav radio as a backup situational awareness tool (technique used by some pilots in the weather in case both FMS's crap out), after the first go around and hand off to approach control for another approach, accidentally toggled nav frequency from ILS to VOR instead of comm frequency, and never set it back because of task saturation. But if that were the case, the primary flight displays would be showing different indications if one pilot had ILS freq and the other had VOR freq. If they originally went missed for being unstable, they seem like the prudent type of crew to go missed for conflicting data on primary displays if VOR was accidentally tuned. But... why they didn't go missed at or below mins the second time is a big surprise. Definitely human factors going on. Hopefully the findings will be public one day, lot of questions about this one. Glad tower saw it and made the call.
Juan,
Great report - thank you!
BTW April 1 readings for MA reservoirs - Quabbin: 100.9 percent Wachusett: 92.3 percent
Paul (in MA)
Looking forward to the final report- this is bizarre, especially from SWA.
The pilots union reps are being put to work on this one -
at best, a "training opportunity/requirement", or if the FO is probationary/new, that pilot is toast, I predict.
Flown into LGA a ton of times, never had an issue with alignment.
...though I messed up pretty damn good with both alignment and height once during a visual approach as a new FO on a beautiful day :)
Juan might be right -
Using autopilot, although prohibited by the approach plate?
Also per Juan, they dropped below DH when the go-around order was commanded.
If the FAA wants some answers, they'll be talking to pilots union/southwest's lawyers.
unlikey there will be any disciplinary action for either pilot. Sheesh. They did their ASAP reports, etc, no reason it would not be accepted by the gatekeeper, it was not an intentional or deliberate act.
@@skyboy1956 For their sake, hope you're correct.
I know a probationary pilot who was not the pilot flying, but the aircraft had a no injuries incident flying out of LAX during climb out.
Flash icing, stall, then inverted in IMC. Regional turbo-prop, so no Piccolo tubes/hot bleed air.
Not yet under union protection, the union advised him to quit immediately, but the airline fired him one day after he resigned.
Took 6 months to clear up, and keep his record clean.
No indication from FAA's AIN notices or the NTSB that they're even actively investigating this which is wild.
Big divert to burn off the 737 tapes??
Blanco should have followed the rest of the flight..
@@user-pf5xq3lq8i they said their alt was Pittsburg which that being their alt in their flight plan is completely possible
LGA-PHL is shorter than LGA-PIT
@@skyboy1956 Why wouldn't they just divert to Kennedy or Teterboro?
Most likely because the wx at those airports was similar and their fuel situation dictated they go to a further better wx destination.
The ATC audio is confusing. Which pilot was the captain? One would rightly assume that the captain would be flying in this mess, particularly at LGA, and the FO would be working the radio, which would make the female the captain, but the female doesn't sound very experienced on the radio, at least. Contrast Tammy Jo, who, while kinda sing-songy, was very clear, calm and affirmative in her radio patter (and a complete hero, of course -- just so impressed with her).
Female FP and captain flying the HUD. She is shaken and instead of her tellling the FO to tell ATC
About diversion she just did it herself. Male voice is shaken FO/PM.
ATC was the voice asking twice to two different flights the reason for the go around As per their requirements. Why were they off course?
I’ve flown the shuttle and that approach about 3000 times17 years DC-9, A320. Never seen LOC deviation.
Just excellent, Juan. Some further info needed. Thanks for your comment.
Thanks Juan. Good job. Lots of unanswered questions here. Some questions can not be asked nor even be considered if you get my drift. Been there done that. Good luck to all the new major airline Captains keep the blue side up.
This is a remarkably concerning incident. Thanks to Juan and the many knowledgeable commentators for their considered input to the discussion. I look forward to further analysis and official investigation report. I do fear and feel that the clock is ticking and the Swiss cheese holes will align again one day in US airspace on a busy commercial flight. I sincerely hope that I’m wrong. I commend the controller taking over the position, although no doubt she will take some flak for missing the appropriate call sign.
Perhaps the controller used a blind (no call sign) go around call because she didn't know which aircraft's nose gear was filling her tower cab window, and there was no time to inquire. I've heard the "GLIDESLOPE GLIDESLOPE" warning call out. Is there one for "LOCALIZER LOCALIZER"❓
There needs to be rapid action by FAA to push forward rulemaking on FDR/CVR upgrades to require 24 hours of data capture; AND supplemental rulemaking (because of the normal grandfathering of 1000s of units that will be exempt) that offers a less impactful software/hardware fix on current FDR/CVR units that permits 'bookmarking' a 30-minute window of data upon ATC command (accompanied by appropriate regulatory requirement for such command to be followed without exception).
But FAA normally ignores the "free of fatality" red flags, preferring to wait until they have actual blood on their hands before initiating years of NTSB urging.
I was looking for this comment...worth the search. This incident along with the SFO/Air Canada Flt759 and Alaska Flt 1282 require FDR/CVR data preservation.
7:35 notice both the pilot and the pilot making radio communication. Makes me wonder about the cockpit around this time.
"Stand by......time to bust out the big mouse"....
lol....
...."breaking out of the weather...... and coming right at them...''....yup, that gives us a great visual of what the ATC was facing😳!! And with seconds to spare.....wow.
"....what were the reasons for the 2 go around...?"
I HOPE that was someone else!
Great analysis as always....thanks, Juan!
And even my dog knows, WHENEVER she hears your voice, she might as well find a good spot to sleep for the afternoon-- Mama"s probably heading down yet another aviation rabbit hole!✌🏽❤🔥
BUT!
If she hears the Air Safety Institute guys, she knows THAT MEANS, we're heading out on a walk.......and she hangs out by the front door, taunting the cat that she gets to go to the park, lol. 😆
My God. That was close to being the biggest airline tragedy we've had in quite some time here in the States.
At least in the past 20 years.
that you are aware of.
Female PF…