Quick lesson guys, when a "Go around" takes place it's a completely safe and normal procedure. Usually it's because of weather or they are a little low or high. If you experience it you're fine, it happens a lot.
Oh, I totally understand what that girl was going through. I remember flying from Paris to NYC via Air France Boeing 777 in Dec 2003. The plane was landing and we were able to see the runway, other planes and everything in plain view; the plane was that close to to touching on the ground. Suddenly, the plane cruised back into the air at a very high altitude. I was so scared. Five minutes later, the pilot spoke but it was only in French. As an exchange student returning from Spain that fall semester, I did not understand one word that was spoken by the pilot. Eventually, he said in English that due to bad whether we were not cleared for landing. The passenger who sat next to me comforted me. If a female on here who paid a visit to reunite with her birth mother in Hungary and remember comforting a young college student in 2003 on an air france flight, thank you.
As a San Diego resident, I can tell you this is rather common as we have one runway as someone mentioned. Nothing wrong with the plane. When you have a city the size of SD with such a small airport, sometimes you gotta circle a bit before you can land.
Not really, it was most likely just because the pilot was unstable or they were a little low on the glide slope. It's not because of the size of the airport, although I do agree that the airport can be more challenging due to the steep approach. I understand how this could happen more at San Diego (KSAN) than other airports.
Well, I'm assuming that this girl didn't understand what was happening, soo....yeah. If it were me, I'd be celebrating because I just got a bonus approach into San Diego. :)
Too high, too fast...unstabilized...go around. Nice to see San Dog again. Stationed here in the 80's, Naval Aviation, Connie. Should have bought property there back then. 😎
@@lewisroper8668 If he was too high, I'm not sure he would admit it. "Another plane on the runway" blaming the controller (or another pilot) gets him off the hook with the passengers and his bosses at Southwest.
Imagine a city the size of SD, still has an Airport with one runway, I've had 2 aborted landings there. One was aircraft on runway, the other was faulty nosegear warning light.
Yes its annoying to say the least that SD has only one runway too much local city council politricks.City was offered Miramar site and a few land pieces to the south but refused. Its annoying that on foggy days only RNWY 9 is available for ILS and some heavies still have to depart RNWY 27 since two heavy so you have traffic alternating and severe delays 🤬.
I don't know about scary. The pilot peeled off of that approach pretty early. I've gone around in San Diego when we were floating above the runway for awhile and then they added power and we climbed out, did a series of left turns and came in for a landing. The pilot came on and said "well folks, we're going to try that again, a little lower and a little slower". That was a little alarming. My most scary go around was in Newark (high winds) where the wheels actually touched and we climbed back out and went around.
This is an ATC mistake 100%. I've been in the SouthWest jumpseats many times and one memory in particular comes to mind ... going into Denver approach control switched us from landing 34 to 8. Result was high and fast. FO was flying and the captain immediately told him to be ready for a go-around. By 3000 AGL it was clear we were way too high and fast so they went around and got sequenced back in and everyone went about their business that day.
That's a textbook too fast too high event. The aircraft was doing s turns to increase the total distance to the runway while the engines remained at idle thrust. You can see how high the plane is as he makes his base to final turn, and with no flaps too, so he must be going at least 200 knots. As for not announcing the reason for the go around, there is a set of items to prioritize while you are flying an airplane. Aviate, Navigate and Communicate in that order. Letting the passengers know whats going on isn't even on that list of priorities and is only even thought about if you've got some free time, like on an extended downwind leg. People are scared of what they don't understand, and if you pay attention and start picking up things that happen on an airplane and understand why they are happening, then I think you'd feel a lot better about similar situations. :D
I thought I was the only one to not see > flap deployment. SWA knows that airport better than most................supposedly. Their equipment though isn't enough to make a poor visibility landing. This was told to us by a TWA captain on approach from the ocean into visibility so poor you couldn't see a thing till we touched the runway. At least he alerted us to a good chance of a go-around before we got onto final approach. Told us exactly what to expect during an aborted landing--sounds and all.
@Daniel You obviously know nothing lol. It isn't the captain himself who sets himself on the base leg, it's the approach controller (in this case it's socal approach. It isn't difficult at all to capture a localizer, it's simple instrument flying. It's socal that gives altitudes, headings, etc, to set themselves up for the localizer; and socal is known for giving the visual and the rnav a lot instead of the loc approach.
SWA policy; if you’re going to use the boards, you must not have any flaps out. However, I didn’t see any speed break panels deployed. The speed breaks never did much for me on the 737 other than make a bunch of vibrations. She doesn’t like to go down and slow down...
Geez, that wasn’t even close. Abort came about 1 mile final. Only a couple of reasons. The S turn right before gives a good clue. And as the pilot said, another airplane on the runway. That happens a couple of ways. Because SAN has only one runway departures have to be spaced with arrivals. If you have two landing and one departure in between you need the first lander to clear the runway as soon as safe. You will have the departure “line up and wait” while the lander is rolling out. As soon as he exits the departure is cleared. Now if the lander is slow getting off the runway he can mess it up for both the other guys. If the departure takes his time getting lined up and isn’t ready to go right away he can mess it up for both him and the lander as well. Retired 30 years ATC Chicago.
I know the feeling of going around. Back in 2009 I flew to NY JFK from Ft. Lauderdale FLL on JetBlue, we were going around for about an hour because the airport was shut down due to severe storms. It was pretty frightening.
When the flight crew turned to base at 5000 ft and little or no flaps, I was doubtful of the approach. When they turned to final still above way above 2000 ft and no full flaps, I was definitely skeptical. When they couldn't bring it down to buzz the Air and Space museum I knew they couldn't make the field. If SoCal brings me high and tight I want to be at 150 knots, full flaps and gear down. The runway elevation is barely a few feet above sea level, your pattern altitude is Laurel street (terrain).
While it doesn’t normally happen, it does happen when needed. But, it is right. I’ve been on a couple go arounds, several things can cause it, from not being able to see the runway, too strong of a cross wind, plane still on the runway. One of Th times for me was for visibility, the other was probably a plane on the runway (LHR morning rush).
SoCal Approach often will drop us into the 27 approaches high and fast ... from my experience, if it is visual conditions you can manage but I've also had them do it in IMC. This video does not surprise me one bit.
Are typical night landings at SAN on 9? A science professor tried to explain to me why winds change over night on coastlines, he still could be talking it would still be way over my head.
@@dpm-jt8rj Most approaches are on 27 due to the normal west breeze. If there's a Santa Ana (wind from the east), then it's 9. Day or night doesn't matter. However, fog (or low clouds as the locals call it) often rolls in at night. If the ceiling is
His approach was too high. I know this approach well. I lived in San Diego in the late 90's. My condo was on 3rd Ave. between Grape and Fir streets. Basically....right below the point where he throttled up. That round white building you see in the video....right before the throttles up is the San Diego Air and Space Museum in Balboa Park. His approach at this point is rather high.
OK they applied power as they were crossing 6th street, there was another aircraft on the runway, great reason to go around. Ground control must have screwed up or maybe another pilot of that plane misunderstood his or her instructions and moved into takeoff position on the runway after being told to HOLD SHORT. In any case, the go around was for safety reasons. Would have wondered if I was on the plane, but would not have been scared. Would have known there was a reason and the pilot explained what it was. Then again, no matter what the pilot announced, it did perhaps seem like the pilot may have been trying to extend his time in the approach glide slope and never did deploy the flaps, so I'm guessing the plane was on the runaway already and supposed to have taken off but didn't get off in time and that played a role in the decision to go around perhaps?
I know why she was panicking usually the pilot always let the passengers know what his doing every move every decision he always let them know before he does something I’m surprised the pilot gave the announcement pretty late. If the pilot let the passengers know what’s going on in the first place I’m pretty sure she wouldn’t be freaking out .
You said the reason why. Alcock and Brown made a JOINT flight across the Atlantic. Lindbergh, who's plane was built here and who first flew it here, was, however, the first solo, non-stop transatlantic flight, and one made between two major cities, and by a man barely 25 years of age. Ryan Aircraft Company of San Diego agreed to design and build a custom monoplane for $10,580, and on February 25 1927 a deal was formally closed. Dubbed the Spirit of St. Louis, the fabric-covered, single-seat, single-engine "Ryan NYP" high-wing monoplane (CAB registration: N-X-211) was designed jointly by Lindbergh and Ryan's chief engineer Donald A. Hall. The Spirit flew for the first time just two months later, and after a series of test flights Lindbergh took off from San Diego on May 10. He went first to St. Louis, then on to Roosevelt Field on New York's Long Island.
The pilot announced it at the very end the go around was due to another aircraft on the runway. Yes Aviate, Navigate then communicate. Safety first!
Exactly!
Quick lesson guys, when a "Go around" takes place it's a completely safe and normal procedure. Usually it's because of weather or they are a little low or high. If you experience it you're fine, it happens a lot.
Or if there's a plane still in the way on the tarmac and it hadn't cleared yet.
Not a lot
Or somebody is on the runway...
Very common, usually a tower/ATC issue, relax folks, we'll have you down and eating the best fish tacos ASAP
Oh, I totally understand what that girl was going through. I remember flying from Paris to NYC via Air France Boeing 777 in Dec 2003. The plane was landing and we were able to see the runway, other planes and everything in plain view; the plane was that close to to touching on the ground. Suddenly, the plane cruised back into the air at a very high altitude. I was so scared. Five minutes later, the pilot spoke but it was only in French. As an exchange student returning from Spain that fall semester, I did not understand one word that was spoken by the pilot. Eventually, he said in English that due to bad whether we were not cleared for landing. The passenger who sat next to me comforted me. If a female on here who paid a visit to reunite with her birth mother in Hungary and remember comforting a young college student in 2003 on an air france flight, thank you.
As a San Diego resident, I can tell you this is rather common as we have one runway as someone mentioned. Nothing wrong with the plane. When you have a city the size of SD with such a small airport, sometimes you gotta circle a bit before you can land.
I live right under the flight path of Lindbergh Field. There has been a debate for years about moving the airport, but it has never happened.
Not really, it was most likely just because the pilot was unstable or they were a little low on the glide slope. It's not because of the size of the airport, although I do agree that the airport can be more challenging due to the steep approach. I understand how this could happen more at San Diego (KSAN) than other airports.
Can't believe how much San Diego has grown since my lat visit in 1980.
Well, I'm assuming that this girl didn't understand what was happening, soo....yeah. If it were me, I'd be celebrating because I just got a bonus approach into San Diego. :)
This happens quite often - nothing to worry about. Rather have a go around than a collision with another plane.
Dave Contarino that approach was to high
Too high, too fast...unstabilized...go around.
Nice to see San Dog again. Stationed here in the 80's, Naval Aviation, Connie. Should have bought property there back then. 😎
@@naudit1634 listen to the captains announcements you van literally hear him say they was another plane in the runway
@@lewisroper8668 If he was too high, I'm not sure he would admit it. "Another plane on the runway" blaming the controller (or another pilot) gets him off the hook with the passengers and his bosses at Southwest.
Imagine a city the size of SD, still has an Airport with one runway, I've had 2 aborted landings there. One was aircraft on runway, the other was faulty nosegear warning light.
Yes its annoying to say the least that SD has only one runway too much local city council politricks.City was offered Miramar site and a few land pieces to the south but refused. Its annoying that on foggy days only RNWY 9 is available for ILS and some heavies still have to depart RNWY 27 since two heavy so you have traffic alternating and severe delays 🤬.
@@Arsenalusa The only time Miramar was offered to San Diego was in 1954 (for $1).
I don't know about scary. The pilot peeled off of that approach pretty early.
I've gone around in San Diego when we were floating above the runway for awhile and then they added power and we climbed out, did a series of left turns and came in for a landing. The pilot came on and said "well folks, we're going to try that again, a little lower and a little slower". That was a little alarming. My most scary go around was in Newark (high winds) where the wheels actually touched and we climbed back out and went around.
This is an ATC mistake 100%. I've been in the SouthWest jumpseats many times and one memory in particular comes to mind ... going into Denver approach control switched us from landing 34 to 8. Result was high and fast. FO was flying and the captain immediately told him to be ready for a go-around. By 3000 AGL it was clear we were way too high and fast so they went around and got sequenced back in and everyone went about their business that day.
That's a textbook too fast too high event. The aircraft was doing s turns to increase the total distance to the runway while the engines remained at idle thrust. You can see how high the plane is as he makes his base to final turn, and with no flaps too, so he must be going at least 200 knots. As for not announcing the reason for the go around, there is a set of items to prioritize while you are flying an airplane. Aviate, Navigate and Communicate in that order. Letting the passengers know whats going on isn't even on that list of priorities and is only even thought about if you've got some free time, like on an extended downwind leg. People are scared of what they don't understand, and if you pay attention and start picking up things that happen on an airplane and understand why they are happening, then I think you'd feel a lot better about similar situations. :D
Aidan Hutchison yea the reason was as you said and he did a shitty job capturing the LOC damm Ryanair I mean Southwest lol
I thought I was the only one to not see > flap deployment. SWA knows that airport better than most................supposedly. Their equipment though isn't enough to make a poor visibility landing. This was told to us by a TWA captain on approach from the ocean into visibility so poor you couldn't see a thing till we touched the runway. At least he alerted us to a good chance of a go-around before we got onto final approach. Told us exactly what to expect during an aborted landing--sounds and all.
@Daniel You obviously know nothing lol. It isn't the captain himself who sets himself on the base leg, it's the approach controller (in this case it's socal approach. It isn't difficult at all to capture a localizer, it's simple instrument flying. It's socal that gives altitudes, headings, etc, to set themselves up for the localizer; and socal is known for giving the visual and the rnav a lot instead of the loc approach.
SWA policy; if you’re going to use the boards, you must not have any flaps out. However, I didn’t see any speed break panels deployed. The speed breaks never did much for me on the 737 other than make a bunch of vibrations. She doesn’t like to go down and slow down...
Aidan Hutchison i
Geez, that wasn’t even close. Abort came about 1 mile final. Only a couple of reasons.
The S turn right before gives a good clue. And as the pilot said, another airplane on the runway.
That happens a couple of ways. Because SAN has only one runway departures have to be spaced with arrivals. If you have two landing and one departure in between you need the first lander to clear the runway as soon as safe. You will have the departure “line up and wait” while the lander is rolling out. As soon as he exits the departure is cleared.
Now if the lander is slow getting off the runway he can mess it up for both the other guys. If the departure takes his time getting lined up and isn’t ready to go right away he can mess it up for both him and the lander as well.
Retired 30 years ATC Chicago.
Starting at 6:47, you will be able to see SeaWorld.
I know the feeling of going around. Back in 2009 I flew to NY JFK from Ft. Lauderdale FLL on JetBlue, we were going around for about an hour because the airport was shut down due to severe storms. It was pretty frightening.
It happens. I've seen a few of those at D/FW from time to time.
Happened to me today flying into San Diego. I was a little shook up but ok after the pilot announced what happened
Not exactly sure what led to this but SoCal approach does bring us in high and tight very often to this airport
When the flight crew turned to base at 5000 ft and little or no flaps, I was doubtful of the approach. When they turned to final still above way above 2000 ft and no full flaps, I was definitely skeptical. When they couldn't bring it down to buzz the Air and Space museum I knew they couldn't make the field. If SoCal brings me high and tight I want to be at 150 knots, full flaps and gear down. The runway elevation is barely a few feet above sea level, your pattern altitude is Laurel street (terrain).
Ralph Valeron you sir, are a genius
While it doesn’t normally happen, it does happen when needed. But, it is right. I’ve been on a couple go arounds, several things can cause it, from not being able to see the runway, too strong of a cross wind, plane still on the runway. One of Th times for me was for visibility, the other was probably a plane on the runway (LHR morning rush).
somebody was a little scared... hehehehehehe
Fuck both of you. She did well.
Adam Pfaff She has to do well. What else CAN she do jump off the plane??? She’ll never go flying again.... or will she?
Adam Pfaff Beta male alert
For the record. An aborted landing is a go around, an aborted go around is a landing.
SoCal Approach often will drop us into the 27 approaches high and fast ... from my experience, if it is visual conditions you can manage but I've also had them do it in IMC. This video does not surprise me one bit.
Cool video. Great view of SD - I always end up with flights landing at night.
Are typical night landings at SAN on 9? A science professor tried to explain to me why winds change over night on coastlines, he still could be talking it would still be way over my head.
@@dpm-jt8rj Most approaches are on 27 due to the normal west breeze. If there's a Santa Ana (wind from the east), then it's 9. Day or night doesn't matter. However, fog (or low clouds as the locals call it) often rolls in at night. If the ceiling is
I saw an Lufthansa a340 perform a go around at san diego
Carlos Ortiz that’s pretty badass
Latest addition to San Diego airport! I seen a British 747 do a missed but didn't have my camera handy
I've never heard of an aborted go around.
What caused it?
approach looked MILES too high
Mac Borowy I agree Balboa Park looked way too high when they passed it.
What does Aborted Go Around Landing mean I think you meant to say Go Around Landing In San Diego.
His approach was too high. I know this approach well. I lived in San Diego in the late 90's. My condo was on 3rd Ave. between Grape and Fir streets. Basically....right below the point where he throttled up. That round white building you see in the video....right before the throttles up is the San Diego Air and Space Museum in Balboa Park. His approach at this point is rather high.
Lmao that was funny. Poor girl
Ha, we had an aborted landing yesterday on the Lufthansa flight into San Diego, pilot didn't even say the reason!...
Rob Sevilla Dang the 340 already went around here!
Nice video. Subscribed
The plane looked incredibly high to land from the beginning, most likely pilot overshot it
Higher tentions on 9/11....
OK they applied power as they were crossing 6th street, there was another aircraft on the runway, great reason to go around. Ground control must have screwed up or maybe another pilot of that plane misunderstood his or her instructions and moved into takeoff position on the runway after being told to HOLD SHORT. In any case, the go around was for safety reasons. Would have wondered if I was on the plane, but would not have been scared. Would have known there was a reason and the pilot explained what it was.
Then again, no matter what the pilot announced, it did perhaps seem like the pilot may have been trying to extend his time in the approach glide slope and never did deploy the flaps, so I'm guessing the plane was on the runaway already and supposed to have taken off but didn't get off in time and that played a role in the decision to go around perhaps?
I know why she was panicking usually the pilot always let the passengers know what his doing every move every decision he always let them know before he does something I’m surprised the pilot gave the announcement pretty late. If the pilot let the passengers know what’s going on in the first place I’m pretty sure she wouldn’t be freaking out .
What a nightmare...
I wonder why they didn't name the airport after the first men to fly the Atlantic non-stop eight years before Lindbergh, oh I know, they were British
maria cornwallis
This is the United States...
You said the reason why. Alcock and Brown made a JOINT flight across the Atlantic. Lindbergh, who's plane was built here and who first flew it here, was, however, the first solo, non-stop transatlantic flight, and one made between two major cities, and by a man barely 25 years of age. Ryan Aircraft Company of San Diego agreed to design and build a custom monoplane for $10,580, and on February 25 1927 a deal was formally closed. Dubbed the Spirit of St. Louis, the fabric-covered, single-seat, single-engine "Ryan NYP" high-wing monoplane (CAB registration: N-X-211) was designed jointly by Lindbergh and Ryan's chief engineer Donald A. Hall. The Spirit flew for the first time just two months later, and after a series of test flights Lindbergh took off from San Diego on May 10. He went first to St. Louis, then on to Roosevelt Field on New York's Long Island.