IRROPS due to no-show pax - Delta's responsibility?
#1
Original Poster
Join Date: Jul 2014
Location: Anywhere with mountains
Programs: DL PM, Hertz 5*, SPG
Posts: 328
IRROPS due to no-show pax - Delta's responsibility?
Flying SLC-JFK-CDG-BOM last week with last two segments in W on AF metal. Right before boarding in SLC, get a text that JFK-CDG is delayed 1 h, putting my transfer at risk. From my seat on the plane, I call PM line, and it sounds like the incoming flight from CDG-JFK is delayed 3 h due to "technical issues" and also having to remove the bag of a no-show pax. With the 3 h delay, no chance of making CDG-BOM. However, won the phone agent lottery that day, as she offered to switch me to the JFK-AMS-BOM, which actually arrives an hour earlier. I asked if I could be re-booked into J, since I was in W previously and it would be a shame to downgrade to Y in an IRROPS, and got a "sure, I can do that" (!) Definitely gave a JWD cert for this one, as I flew JFK-AMS-BOM all in BE.
Anyhow, the IRROPS actually got stranger from there, as our AMS-BOM had to divert to Munich for a passenger emergency. Didn't impact my trip too badly as it was on last leg, but we arrived 3 h delayed. However, this made me think about the question of whether IRROPS due to pax issues (no-show or flight diversion due to emergency) is considered the carrier's responsibility. In the case of my original IRROPS, info also showed "technical issues" so it was solidly in the court of DL responsibility, but what happens when it is only pax issues? Is it treated like a Mx (hotel, vouchers) or a Wx (nada)?
TL;DR - Had an interesting IRROPS experience - curious whether delays due to pax issues warrant hotel/vouchers from DL, or whether this is equivalent to Wx delay.
Anyhow, the IRROPS actually got stranger from there, as our AMS-BOM had to divert to Munich for a passenger emergency. Didn't impact my trip too badly as it was on last leg, but we arrived 3 h delayed. However, this made me think about the question of whether IRROPS due to pax issues (no-show or flight diversion due to emergency) is considered the carrier's responsibility. In the case of my original IRROPS, info also showed "technical issues" so it was solidly in the court of DL responsibility, but what happens when it is only pax issues? Is it treated like a Mx (hotel, vouchers) or a Wx (nada)?
TL;DR - Had an interesting IRROPS experience - curious whether delays due to pax issues warrant hotel/vouchers from DL, or whether this is equivalent to Wx delay.
#2
A FlyerTalk Posting Legend
Join Date: Sep 2009
Location: Minneapolis: DL DM charter 2.3MM
Programs: A3*Gold, SPG Plat, HyattDiamond, MarriottPP, LHW exAccess, ICI, Raffles Amb, NW PE MM, TWA Gold MM
Posts: 100,409
I'd expect it to be treated like WX problems. It's not DL's fault, but as usual you might get some apology miles.
However, in your situation, the problem was an AF flight so EC261 rules would apply.
Moreover, it shouldn't take three hours to find and remove a bag. In the past, I never saw a bag removal take even an hour and everything seems quicker now with bar coded bag tags and scanners. Airlines can figure out where a given bag was loaded in the aircraft very easily, although they need to move/remove other bags/cargo to access the given bag. My recent experience is more like fifteen minutes, perhaps with a range of ten minutes to under a half hour.
My guess is that the no show passenger who checked a bag was irrelevant for the delay which was wholly determined by the MX issue.
However, in your situation, the problem was an AF flight so EC261 rules would apply.
Moreover, it shouldn't take three hours to find and remove a bag. In the past, I never saw a bag removal take even an hour and everything seems quicker now with bar coded bag tags and scanners. Airlines can figure out where a given bag was loaded in the aircraft very easily, although they need to move/remove other bags/cargo to access the given bag. My recent experience is more like fifteen minutes, perhaps with a range of ten minutes to under a half hour.
My guess is that the no show passenger who checked a bag was irrelevant for the delay which was wholly determined by the MX issue.
#3
Original Poster
Join Date: Jul 2014
Location: Anywhere with mountains
Programs: DL PM, Hertz 5*, SPG
Posts: 328
I'd expect it to be treated like WX problems. It's not DL's fault, but as usual you might get some apology miles.
However, in your situation, the problem was an AF flight so EC261 rules would apply.
Moreover, it shouldn't take three hours to find and remove a bag. In the past, I never saw a bag removal take even an hour and everything seems quicker now with bar coded bag tags and scanners. Airlines can figure out where a given bag was loaded in the aircraft very easily, although they need to move/remove other bags/cargo to access the given bag. My recent experience is more like fifteen minutes, perhaps with a range of ten minutes to under a half hour.
My guess is that the no show passenger who checked a bag was irrelevant for the delay which was wholly determined by the MX issue.
However, in your situation, the problem was an AF flight so EC261 rules would apply.
Moreover, it shouldn't take three hours to find and remove a bag. In the past, I never saw a bag removal take even an hour and everything seems quicker now with bar coded bag tags and scanners. Airlines can figure out where a given bag was loaded in the aircraft very easily, although they need to move/remove other bags/cargo to access the given bag. My recent experience is more like fifteen minutes, perhaps with a range of ten minutes to under a half hour.
My guess is that the no show passenger who checked a bag was irrelevant for the delay which was wholly determined by the MX issue.
#4
FlyerTalk Evangelist
Join Date: Jun 2001
Programs: DL 1 million, AA 1 mil, HH lapsed Diamond, Marriott Plat
Posts: 28,190
The first issue was the delay in an AF-operated JFK-CDG? If so, this isn't DL's problem for rebooking or compensation. Day of departure disruptions are owned by the operating carrier, irrespective of ticketing party or marketing code.
#5
Suspended
Join Date: Aug 2010
Location: DCA
Programs: UA US CO AA DL FL
Posts: 50,262
This has nothing to do with DL whatsoever and OP is lucky that DL was willing to rebook.
But, even if DL were the operating carrier:
1. The delay due to having to pull a noshow bag is a government security rule (xEU) and not within DL's control at all.
2. The medical emergency is also not within DL's control (presuming that DL didn't poison the guy).
Neither gets OP anything.
But, even if DL were the operating carrier:
1. The delay due to having to pull a noshow bag is a government security rule (xEU) and not within DL's control at all.
2. The medical emergency is also not within DL's control (presuming that DL didn't poison the guy).
Neither gets OP anything.
#6
Join Date: Oct 2009
Location: MCO
Programs: DL DM/MM, Marriott Plat Premier, HH Diamond, Hyatt Plat, Hertz PC
Posts: 4,081
Anyhow, the IRROPS actually got stranger from there, as our AMS-BOM had to divert to Munich for a passenger emergency. Didn't impact my trip too badly as it was on last leg, but we arrived 3 h delayed. However, this made me think about the question of whether IRROPS due to pax issues (no-show or flight diversion due to emergency) is considered the carrier's responsibility. In the case of my original IRROPS, info also showed "technical issues" so it was solidly in the court of DL responsibility, but what happens when it is only pax issues? Is it treated like a Mx (hotel, vouchers) or a Wx (nada)?
TL;DR - Had an interesting IRROPS experience - curious whether delays due to pax issues warrant hotel/vouchers from DL, or whether this is equivalent to Wx delay.
TL;DR - Had an interesting IRROPS experience - curious whether delays due to pax issues warrant hotel/vouchers from DL, or whether this is equivalent to Wx delay.
“What if that was one of us?”
That’s enough for me to take a deep breath and be thankful all I have to deal with is a delay vs this poor soul who may end up in a hospital with no one who speaks their language, no insurance coverage, maybe no family at their bedside, etc.
I wouldn’t have the stones to even think to request RDM’s or hotel voucher but then, I believe in travel karma. YMMV of course.
#7
Original Poster
Join Date: Jul 2014
Location: Anywhere with mountains
Programs: DL PM, Hertz 5*, SPG
Posts: 328
A passenger emergency is not Cx or Mx. It’s a passenger emergency. Seen this happen before and always remember what my wife says…
“What if that was one of us?”
That’s enough for me to take a deep breath and be thankful all I have to deal with is a delay vs this poor soul who may end up in a hospital with no one who speaks their language, no insurance coverage, maybe no family at their bedside, etc.
I wouldn’t have the stones to even think to request RDM’s or hotel voucher but then, I believe in travel karma. YMMV of course.
“What if that was one of us?”
That’s enough for me to take a deep breath and be thankful all I have to deal with is a delay vs this poor soul who may end up in a hospital with no one who speaks their language, no insurance coverage, maybe no family at their bedside, etc.
I wouldn’t have the stones to even think to request RDM’s or hotel voucher but then, I believe in travel karma. YMMV of course.
#8
FlyerTalk Evangelist
Join Date: Aug 2005
Location: BOS/EAP
Programs: UA 1K, MR LTT, HH Dia, Amex Plat
Posts: 32,040
EU reg261 does not apply. The OP chose voluntarily to not take the flight via CDG ... no EU reg261 here. If the OP was on the flight and missed the connection to BOM that's a different story.
#9
A FlyerTalk Posting Legend
Join Date: Sep 2009
Location: Minneapolis: DL DM charter 2.3MM
Programs: A3*Gold, SPG Plat, HyattDiamond, MarriottPP, LHW exAccess, ICI, Raffles Amb, NW PE MM, TWA Gold MM
Posts: 100,409
Of course there's no EC261 comp here, but the OP was asking hypothetically whether DL would treat the situation as MX or WX. I pointed that it was an AF operated flight and, as a flight to the EU on an EU carrier, the case would be covered by EC261 rather than DL's or AF's own policies.
#11
FlyerTalk Evangelist
Join Date: Feb 2000
Location: London, UK and Southern France
Posts: 18,364
It seems to me pretty clear that it is the airline's responsibility to have proper protocols to remove baggage from the aircraft without resulting in undue delay. As the Court of Justice of the EU would put it, this is "part of the normal exercise of the activity of the air carrier concerned" and cannot therefore be regarded as an extraordinary circumstance justifying exemption from the duty to pay compensation.
2. The medical emergency is also not within DL's control
#12
Join Date: Feb 2011
Location: CVG,SDF,LEX
Programs: Delta DM MM
Posts: 772
Moreover, it shouldn't take three hours to find and remove a bag. In the past, I never saw a bag removal take even an hour and everything seems quicker now with bar coded bag tags and scanners. Airlines can figure out where a given bag was loaded in the aircraft very easily, although they need to move/remove other bags/cargo to access the given bag. My recent experience is more like fifteen minutes, perhaps with a range of ten minutes to under a half hour.
#13
Join Date: Dec 2009
Location: RDU
Programs: DL DM+(segs)/MM, UA Ag, Hilton DM, Marriott Ti (life Pt), TSA Opt-out Platinum
Posts: 3,227
It sounds like the bulk of the pax's original delay was MX. Yeah, there may have been some delay to remove a bag, but worst case that shouldn't take more than 30 minutes on a widebody (and they start at Departure -10). DL scans the bags, so they know exactly which can they need to remove. Even if the can is in the deepest position, it shouldn't take more than 15 minutes to retrieve the can, then say another 15 minutes to look through the 25-35 bags in the can, and then put all the cans back into position and close the door, remove the cargo loaders, etc.
This is from my experience managing ramp operations at a hub.
There must have been something else going on there. PPBM (Positive Passenger Bag Match) isn't required domestically. Now if the pax that was removed made a bomb threat, that could change things...
It can be very difficult to find one bag on a narrowbody. There are sometimes hundreds in a pit, and you may have to unload every one until you find the one you're looking for, and then of course load them back up.
This is from my experience managing ramp operations at a hub.
It can be very difficult to find one bag on a narrowbody. There are sometimes hundreds in a pit, and you may have to unload every one until you find the one you're looking for, and then of course load them back up.
#14
A FlyerTalk Posting Legend
Join Date: Sep 2009
Location: Minneapolis: DL DM charter 2.3MM
Programs: A3*Gold, SPG Plat, HyattDiamond, MarriottPP, LHW exAccess, ICI, Raffles Amb, NW PE MM, TWA Gold MM
Posts: 100,409
Why did they remove the passenger and how could that step take so much time? Was there a lot of time spent deciding whether to remove the passenger or not? If so, that would seem unusual as these decisions are usually made quickly and are not subject to reversal or appeal.
#15
Join Date: Feb 2011
Location: CVG,SDF,LEX
Programs: Delta DM MM
Posts: 772
Why did they remove the passenger and how could that step take so much time? Was there a lot of time spent deciding whether to remove the passenger or not? If so, that would seem unusual as these decisions are usually made quickly and are not subject to reversal or appeal.