Originally Posted by
tom188
Hi all. I was on BA2561 SVQ->LGW on Sunday which finally arrived at 23:29 rather than the planned 18:50. The weather was obviously horrible, and we went round at LGW, but the pilot attributed much of the delay of the outbound 2560 to a late arriving previous rotation of 2597 from Turin, and then having a computer problem which needed a reset. Then when we thought we were departing 19:35, we reached the runway but then taxied off again with a further computer issue, and apparently our flight plan was then erroneously deleted so another one had to be lodged, meaning we didn't finally depart until 20:23 vs scheduled 17:05. Could there be grounds for a EC261 claim here or is it likely to be rejected on weather grounds?
On initial reading yes due to the technical faults. The claim will be rejected citing weather. I will look into it further for you when I get a chance to see timings/allocations etc.
EDIT -G-EUXH 21st
2596 LGW-TRN Sector time blocked at 1:55 no CTOT filed and no delay code for the mins off 9 mins late @ 07:59. 18 mins planned taxi. Airborne 8:21. Taxi time actually 22 mins. Planned flight time 1:22. Touch down at 09:41 so 1:20 actual flight time. On stand 09:57 or 12 mins late.
2597 TRN-LGW Sector time blocked at 1:55. Allowed 12 mins RA due late arrival of inbound. Delay codes RA 0012 GA 0042 FRZ 0003. Off stand at 11:32 or 57 mins late. Planned 10 min taxi. Airborne at 11:44 so 12 mins taxi actual. 1:31 planned flight time. Touch down at 13:29 so 14 mins slower than planned. On stand 13:38 vs 12:30 so 1:08 late.
DELAY CODE REASONS RA - Reactionary/GA - Turnaround Coordination/FRZ - flight crew delay (flight crew processes)
2650 LGW-SVQ Sector time blocked at 2:45. Allowed 1:08 of RA due to late inbound. Technical defects noted in remarks and lack of contact made with engineers. Delay codes RA 0108 FR 0138 OFZ 0001.
CTOT issued for 15:40. Departed at 15:17 vs 12:30 and Airbourne at 15:35. Planned taxi time irrelevant due to CTOT. Planned flight time 2:09. Touch down at 17:48 so 2:13 actual flight time. On stand at 17:53 vs 15:15 or 2:38 late.
DELAY CODE REASONS RA - reactionary delay/FR - Flight Crew Special Requests (related to the computer issue)/OFZ - something post doors closed but not allocated a specific reason.
2651 SVQ-LGW Sector time blocked at 2:45. Allowed 2:38 RA due late inbound which would give an off blocks of 18:43 if purely RA delayed. CTOT issued for 2040 with delay codes AW 0039 and GTL 0001.
Actual off block time 1923. Airborne at 20:38. Planned taxi time irrelevant due to CTOT. Planned flight time 2:24. Touch down at 23:18 so actual flight time 16 mins longer than planned. On stand at 23:29 vs 18:50 or 4:39 late.
DELAY CODE REASONS AW - CTOT due weather at destination/GTL - late push back tug arrival.
Weather delays equals 14 mins plus 16 mins due flight times (holding and stronger headwinds than planned) plus 39 mins for the 2561 CTOT AW delay code. The CTOT for BA 2560 is negligible as the BA controlled delay code mins equal the off blocks time, i.e the CTOT was based directly on the updated EOBT or estimated off blocks time, thus not an ATC inspired delay, merely a co-ordination tool. If we were really pedantic we could say that as BA2560 had a planned taxi time of 17 mins. Being off blocks at 15:17 and airborne at 15:35 that’s 18 mins thus 1 extra minute can be down to ATC/weather.
ATC/Weather total therefore 70 mins or 1:10 As weather/ATC can only contribute to 1:10 of delay if pedantry is applied in fullness, you should indeed be in scope for a successful claim as without the BA inspired delays, you’d have only suffered at worst an hour or so delay.