Go-around LFMT yesterday (20100813)
Thread Starter
Join Date: Feb 2001
Location: Leeds, UK
Age: 65
Posts: 37
Likes: 0
Received 0 Likes
on
0 Posts
Go-around LFMT yesterday (20100813)
Excuse me if this is the wrong forum - feel free to move it. Yesterday (13th August) RyanAir FR2472 Leeds/Bradford-Montpellier (LFMT) - approach a little bumpy but nothing too unusual. Low level go-around followed by repeat (successful) approach on same r/w. Approach direction commented on by regulars was very unusual, and go-around over the sea so must have been 13L. Reason given for go-around was wind direction change from mountains. Looking at IAC's for LFMT, there's no ILS for 13, and the VOR/DME chart shows a 6.5% descent. Is that really suitable for a 737-800? It didn't feel like an unusually steep approach to me, though I'm not sure how different it should feel.
METARS around that time of day (around 1300Z):
20100813 METAR LFMT 131100Z 15006KT 120V200 CAVOK 28/07 Q1014 NOSIG=
20100813 METAR LFMT 131200Z 17011KT CAVOK 27/11 Q1013 NOSIG=
20100813 METAR LFMT 131300Z 18009KT CAVOK 27/09 Q1013 NOSIG=
20100813 METAR LFMT 131600Z 17008KT CAVOK 28/09 Q1012 NOSIG=
seems nothing unusual to me, no reports of gusts, and nothing to suggest the mildly bumpy approach we experienced. Anyone know what happened or care to speculate what might have happened - not properly aligned at minimums? Just curious as to the reason - 1st go-around I've experienced in CAVOK conditions - as a passenger that is, done 'em plenty of times myself
METARS around that time of day (around 1300Z):
20100813 METAR LFMT 131100Z 15006KT 120V200 CAVOK 28/07 Q1014 NOSIG=
20100813 METAR LFMT 131200Z 17011KT CAVOK 27/11 Q1013 NOSIG=
20100813 METAR LFMT 131300Z 18009KT CAVOK 27/09 Q1013 NOSIG=
20100813 METAR LFMT 131600Z 17008KT CAVOK 28/09 Q1012 NOSIG=
seems nothing unusual to me, no reports of gusts, and nothing to suggest the mildly bumpy approach we experienced. Anyone know what happened or care to speculate what might have happened - not properly aligned at minimums? Just curious as to the reason - 1st go-around I've experienced in CAVOK conditions - as a passenger that is, done 'em plenty of times myself
Join Date: Jun 2009
Location: a few track miles south of BEKOL
Age: 57
Posts: 140
Likes: 0
Received 0 Likes
on
0 Posts
i have experienced CAVOK goaround due faulty windshear warning. CYUL on BA 747 classic, sometime in oct 99. same warning on second approach but ignored after multiple pireps (and common sense!) indicated no windshear. happens...
Thread Starter
Join Date: Feb 2001
Location: Leeds, UK
Age: 65
Posts: 37
Likes: 0
Received 0 Likes
on
0 Posts
I dare you to post that on the aircrew forum!!!!!
Join Date: Nov 2006
Location: UK
Posts: 246
Likes: 0
Received 0 Likes
on
0 Posts
Be careful with your units: 6.5% sounds steep but it's only about 3.5 degrees which is pretty normal really. As for asking about go-arounds, you're lukcy no one has bitten you yet. Basically they are normal (non)events and there could be a million and one reasons, so just sit back and enjoy the ride.
Join Date: Dec 2000
Location: on the golf course (Covid permitting)
Posts: 2,131
Likes: 0
Received 0 Likes
on
0 Posts
Looking at IAC's for LFMT, there's no ILS for 13, and the VOR/DME chart shows a 6.5% descent. Is that really suitable for a 737-800?
I have flown the approach in a 737, and it is no issue if you are established in the correct configuration at the correct point. However, if you are trying to cut it tight it might be that you end up hot and high, in which case a go-around is the prudent choice.
Now, I am not speculating what happened here, but I would commend any airline for discontinuing the approach if the stabilised approach criteria were not met.
Thread Starter
Join Date: Feb 2001
Location: Leeds, UK
Age: 65
Posts: 37
Likes: 0
Received 0 Likes
on
0 Posts
Oh my God. Was anyone hurt?
I know it was all no big deal, and I did mention at the top it was just a curiosity as to the reason why this everyday occurence happened on this particular occasion. Thanks all for the interesting (and amusing) responses.