Singapore Airlines Flight Delays & Disruptions

[SQfanatic]

IRROPS well handled? weird to notice delays to SQ32, but what's interesting will be how SQ deals with the delayed SQ31 and the south indian bank to BLR, MAA & HYD

Yes, I feel it was well handled. First off, the pilots have to communicate with SIA Engineering but after that, also with the ground staff especially to arrange another gate and different aircraft of the same variant. As far as the return of SQ31, that landed 1 hour past the time Indian flights especially to South India depart. Unfortunately, it looks like lots of passengers have missed their flights and I guess the only option is to put them on the next day morning flight or other partners (namely MAA) assuming they're not full. It'd be a mess I bet. But messier is especially there's no other option to TRV, or even COK (maybe one additional flight). Singapore Airlines should add day flights to other Indian airports too like TRV, COK like the way EK has in the past, not just rely on Scoot.

Fortunately for me, when I took SQ31, I had 7 hours to connect to SQ402, rather than SQ528, so if this was going to Delhi, the layover time would be lesser but still appropriately timed.

[SQ forever]

Many of you are recently aware I took SQ to India this month. I was under the admonition like all my trips that my last leg to SFO would depart on time as always.

I was affected by the following delays ...

IRROPS well handled? weird to notice delays to SQ32, but what's interesting will be how SQ deals with the delayed SQ31 and the south indian bank to BLR, MAA & HYD

[SQfanatic]

Many of you are recently aware I took SQ to India this month. I was under the admonition like all my trips that my last leg to SFO would depart on time as always.

I was affected by the following delays

SQ403 | DEL-SIN | 27MAY 2025 | 9V-SKT

Basically, we pushed back at 9:52PM IST, started our engines but flaps did not retract. I was wondering this is not normal, and our pilot said we had to return to the gate because some passengers chose not to fly and they’d have to offload their bags which took at least 30 minutes.

We ended up pushing back at 10:55PM after almost 1 hour wait time, but the crew communicated when passengers asked especially those with connections. They came around continuously and gave water. Despite the late departure we landed at 6:45AM.

SQ32 | SIN-SFO | 28MAY 2025 | 9V-SMV (Changed to 9V-SJB)

The last time I ever had a delay on my last leg bound to the US was Typhoon Nuri in 2008 (SQ2 via HKG on the 744). This was my second time on SMV on SQ32 (Last time 1/2/2023 with my mom), and looks like SMV had other plans “I just fell sick but one of my other SJ* LR siblings will get you home”. Below is serious though.

But this time it was not weather related. The weather was nice & sunny. We were supposed to pushback for SFO on 9V-SMV at 9:15AM at Gate A15. We were ready a few minutes prior but SIA engineering told the pilots who came with an announcement that we were just ready to go but a technical problem with the actuator, cargo door, etc. It got to the point SMV was not serviceable. Many of you know Changi is busy in the morning so sadly the earliest we would depart is midday (Noon).

The ground staff came onboard and made announcements explaining the problem and SIA engineering could not fix it on time and after negotiating with the pilot, they were supposed to change our gate to gate A1 where SJB was sitting. However the US flights even on the variants SMV-SJI do not depart A1 because of the type of security checks required for US flights. They managed to secure gate A12. They asked us to deplane and head there by 11AM latest.

So I checked iCargo and it was SJB, but SJB was at gate A1, and I had some breakfast (waffles) & as I finished it, it was getting towed and at that time I along with many others entered the gate hold room for another round of security checks. While I got in at 11:15AM, the aircraft took close to another 40 minutes to board (11:55AM). However, we only departed at 12:50PM and got into the runway by 1:10PM.

About how they handled it, this was also done gracefully. A12 had snacks but not what I was considering appropriate for breakfast, but they did give a snack set to all passengers as a token of apology bowing and indicating they were truly sorry.

I was not too upset in fact I was prepared and I didn’t feel the same stress surprisingly and handled it like a pro. But the same can’t be said for the elderly and SIA truly cares about them. Only one gripe was some of the crew unlike my Indian sectors were not very friendly but the Leading stewardess was extremely kind and emphathetic especially sensing many passengers want to get home and said “I will check with the captain and we will pushback soon”. Being a software engineer, I can understand this perspective from every angle and its challenges and what to do at the same time as a passenger - behave with composure and trust.

Part of me is upset I could not land in the morning and work a half day (remotely) and the other part maybe SIA told me we delayed your flight so you can rest up Wednesday afternoon and get ready for Thursday.

If anyone else on this forum was on these 2 flights on the said days, please message me or respond on this thread

[MainlyMiles]

SIA is now flying through Iran airspace again, since 26/27 June. This is resulting in significant time savings of 30-40 minutes on Europe flights, compared to the northern Uzbekistan / Tajikistan detour that also avoided Afghanistan, and without the Afghan capacity constraints almost all Europe flights are now using this new quicker (Iran) routing.

Flights like SQ322 SIN-LHR are now consistently landing on schedule or early for the first time in ages (arrival delays of 30 mins - 1 hour have been common since late March).

However, SIA is sill avoiding Iraq airspace (unlike BA, Qantas, Swiss, etc.), while others like Thai are still avoiding both Iran and Iraq.

[ell3]

So, the question remains: is SQ putting its passengers at risk by being one of the few main carriers that chooses to fly through?
clearly quite a lot of airlines still choose to avoid that airspace completely.

[SQ228]

SIA is indeed using the L750 airway through Afghanistan again (SQ331 just passed through it), which offers a considerable time saving of around 30 minutes on Europe - Singapore flights, compared to the northern Uzbekistan / Tajikistan detour.

Unfortunately capacity is limited because aircraft are restricted to higher altitudes (FL330+) due to security risks and 15-minute spacing between aircraft at the same altitude is applied, because the airspace is uncontrolled (no ATC - so TIBA procedures apply).

The benefit can therefore only be enjoyed by a few flights each day.

Very interesting information. That would make sense then why only select flights are using it as so many SQ flights cross that area at a similar time each day.

[MainlyMiles]

I noticed some SQ flights are now flying across Afghan airspace again. But, the key word: SOME.

Example - SQ23, SQ332, SQ51, SQ377 are flying through as I write. But SQ317…25…327… etc are still making the detour north.

why would this be so?

SIA is indeed using the L750 airway through Afghanistan again (SQ331 just passed through it), which offers a considerable time saving of around 30 minutes on Europe - Singapore flights, compared to the northern Uzbekistan / Tajikistan detour.

Unfortunately capacity is limited because aircraft are restricted to higher altitudes (FL330+) due to security risks and 15-minute spacing between aircraft at the same altitude is applied, because the airspace is uncontrolled (no ATC - so TIBA procedures apply).

The benefit can therefore only be enjoyed by a few flights each day.

[SQ228]

You’re right, SQ23 did go through it. I can also see a Finnair flight about to as well. Yet most planes in the area are bunched up at the southern tip avoiding Afghan airspace, including PIA and Turkish both making a sizeable deviation on the way to ISB.

[ell3]

I noticed some SQ flights are now flying across Afghan airspace again. But, the key word: SOME.

Example - SQ23, SQ332, SQ51, SQ377 are flying through as I write. But SQ317…25…327… etc are still making the detour north.

why would this be so?

[SQ228]

SQ346 is currently around 5 hours late heading to ZRH. It appears from looking across a few sources that it was rescheduled a few times during the night, leading to a 0645 eventual departure which must have been a fun night spent at Gate B8.

Perhaps a technical failure that went long enough to exceed the crew’s shift limits? They might need to get another 77W out of storage to replace SWM.

[SQ228]

Well it’s interesting that 9V-SGG hasn’t flown since the altered flight via BKK. I’m wondering if it returned empty or with passengers?

9V-SGD seems to be the second ULR getting its overhaul as it hasn’t flown in over a week. I think they can stretch 5 aircraft out across the ULR schedule and still make it work.

[yflyer]

I’ll take a wild guess… could it be something like ridiculously strong headwind prediction, which would push the limits on fuel? Crew change would be needed at the point of refuelling and BKK seems to be a location they like using for that.

I can't find any news or articles about this, but what you have said sounds very plausible! From flightradar24.com (link) the flight landed in BKK, then took off an hour later headed for Singapore, where it landed at 7.29pm local time, about 2 hrs 45 min later than the scheduled SQ21 EWR-SIN arrival time of 4.45pm.

[SQ228]

I’ll take a wild guess… could it be something like ridiculously strong headwind prediction, which would push the limits on fuel? Crew change would be needed at the point of refuelling and BKK seems to be a location they like using for that.

[fablee]

DELETED

[fablee]

Just wondering why what was supposed to be non stop Sq21 to SIN has become SQ9033 to BKK.Screenshot_20240515_222300_Flightradar24.jpg