The LHR schedule ex MAN for winter is currently showing quite significant reductions over last winters ops at the moment. This could be that the schedule is still work in progress, but at the moment, the second nightstopper that operates in winter is showing operating in only a few days of the week. Some days are showing as low as 6/day mid week as opposed to 9/day last year.

Have you seen the weather?

I don't know for certain, but guessing the BACF's mostly night-stop in LCY. If they all departed they'd probably have struggled to get them all back in again, meaning they'd have aircraft displaced for this morning also. All the non-based airlines will of course try to get out wherever possible, they don't want to be stuck in LCY when they need to be in say AMS, DUB etc. for this morning.

BRS - Florence
 

FLR is a poor choice of airport. Unfortunately its short runway and susceptibility to inclement weather mean that a disproportionate number of flights end up getting cancelled or diverting to PSA. Hopefully once the runway extension is built it will alleviate the situation to some degree.
Depending on the operating aircraft type, some operators get more penalised than others.

Thanks for the info - I was not aware that this Friday schedule to GLA is not the exception, but the norm:
BA8730 LCY 21:00 - 22:20 GLA
BA8740 LCY 21:15 - 22:35 GLA
BA2210 LCY 21:30 - 22:50 GLA

Bristol to Florence
 

Looking at FR24 E170 G-LCYG operated LCY-FLR three hours late this morning. It then operated FLR-BRS arriving at the latter at 1544 (sched arrival 1225). Instead of returning to FLR with Italy-bound passengers from BRS the flight is shown as cancelled.

All that is shown for the aircraft on FR24's aircraft flight history page is that it departed BRS at 1647 this afternoon with no destination shown. The page shows its next work as STN-FLR tomorrow morning so I'm assuming it went there from BRS.

The BRS website arrivals page shows the FLR-BRS as 'Arrived' but there is no information regarding its deparure on the airport's departures page except the unhelpful note 'Go to Departures' which has been in place since this afternoon.

A poster on another website who was due to travel with his family today said he received an app message from the airline saying today's FLR-BRS was cancelled.

Could this have been a crew hours issue bearing in mind the late running of the earlier sectors?

Yes, I think your correct as the crew must have been out of hours due to the delay and the London City to Florence & Florence to Bristol sector. I feel sorry for the poor passengers once again.

Last weekend's flight was delayed overnight from Saturday afternoon to Sunday morning too, not good performance!

It doesn't really gel, criticising a carrier based at London City, of all places, for operating to an airport with a short runway and liable to weather disruption ...

Hope the flight works out well next week. Please share your experience when you return. Enjoy Florence.

Last week the BRS-FLR sector was cancelled because, it was presumed, crewing hours were an issue after the FLR-BRS sector landed at the latter nearly three and a half hours late. Today the FLR-BRS sector landed at BRS either 76 minutes late or 78 minutes late, depending on whether FR24 or the BRS website is the more accurate.

As has been said, the BRS-FLR sector was then cancelled. Do airlines now operate to such tight crewing schedules that a delay of just over an hour will put crews 'out of hours'?

I saw this go, on time, from LCY, at 0700 this morning. It overnights there and seems to start on time, then sits in Florence for hours for some reason.
Seems third consecutive week - not just 4 Aug and 28 Jul, but 21 Jul as well, when the inbound had arrived at Bristol just 50 minutes late. Only a three sector day, not four, so not quite apparent how the crew can be out of hours. It then overnights at Florence and does a return Stansted on Sunday morning, and then back to LCY.

Being off from LCY to Skiathos JSI in a couple of weeks, a significantly longer sector, beyond Athens, we hope for the best ...

Yesterday they hired a Carpatair F100 to do the IBZ-MAN flight. Perhaps Cityflyer has been overly optimistic with their scheduling of the Embraers, or there is a broken one somewhere

And equally knackered ground staff dealing with delayed , cancelled and flights arriving with NO baggage.
Why schedule an aircraft on a route if its not within its capabilities.

But Bristol to Florence is quite within its capabilities. Its not like there's a short departure runway as there is at LCY earlier in its day's rotation.

Back in the supposedly "bad old days" of IT flights at least the various flights were carried out, maybe late if the inbound was so. If there happened to be insufficient performance on the day (like One-Elevens operating to Tenerife) then a fuel stop was arranged. But this is only 725nm, less than half the E-170s typical max payload range.

This doesn't quite seem to add up. The morning LCY-Florence is due to depart 30 minutes before the Milan gets in, in fact it departs shortly after LCY opens, so the crew must have overnighted at LCY.And if "a" crew member then called in sick, why was the whole crew replaced by one which had come in overnight from Milan. Did the whole crew call in sick ?

I have heard this one before, that someone has "called in sick", when in fact it's nothing of the sort, but a mess-up by crewing.

Do Cityflyer have some Italian-based crew ? Not an idle question; a few years ago I was surprised to find that Cityjet at LCY on the 146 also had so (after a very fluent bilingual PA announcement on one of their flights to Italy), and some of their rosters through LCY were crewed from that end. LCY is a difficult place to retain staff, as we know much of Cityflyer's hub there is actually crewed from Scotland.

It's very good that tghe crew support last-minute mess-abouts like this. One hopes that crewing and management have a similar positive attitude back to them.

But the 7.15am flight from LCY to Florence didn't depart on time, yesterday the flight left 1hr 35min late. Sounds like they were waiting for the crew from the Milan flight so no overnight at LCY.

Indeed. But it doesn't just tie with one crew member reporting sick that morning, if they were waiting for a whole crew.

sounds like it and possibly faster than calling in from standby (IF they even had someone on SBY - Do BACF have airport stand by crew like at BA at LHR and LGW?)

The Florence crew were possibly then used on a later flight with a standby that was called in to make up the numbers

Crewing is a nightmare (i used to do it) and although if you only have 50 pax you can go with just 1 CC member, but if you have a Club Europe load to look after as well then you def need more than 1 CC.

to add
to have airport standby crew is not ness the best option as the longer they sit around waiting then the less duty hours they can be used for - whereas calling from home mean max duty hours apply (but dependant on time of day etc and whether they have a day off booked next day and more)
but it was not common to roster SBY to day off

rog747 - in my day, cabin crew minimum numbers was dictated by number of seats fitted - minimum one CC per 50 seats regardless of number of pax so on a 50 (or less) seat aircraft one CC OK but a 51 seat aircraft minimum two CC. Have the rules changed? PS we could config our a/c down to 100 seats (changing 6 abreast to 5 abreast) and in extremis go with two CC and minimal service.