My suspicion with no evidence or proof beyond human nature: Another passenger panicked upon seeing in a Muslim and said something to the FA. FA has TSA reclear just to be sure. Whatever happened, there is likely a lot of fault to go around, none of it on the family (my guess, but I would bet on this one).
Sure. But what's interesting is, it appears the TSA itself is not at fault this time. No indication that their inquiry, if any, was slow.
"Another passenger" may be partially "at fault," but much more important is jetBlue's reaction to what he or she theoretically said. The FA's reaction at that point would be jetBlue's first fail.
FA behaves badly, but is not only excused by jetBlue, but their press arm issues falsehoods (incriminating the hated TSA) to cover up that bad behavior. Fail exponentialized (sp? a real word?).
No, not a lot of fault to go around. Pretty much all one place. It would appear.
Sure. But what's interesting is, it appears the TSA itself is not at fault this time. No indication that their inquiry, if any, was slow.
"Another passenger" may be partially "at fault," but much more important is jetBlue's reaction to what he or she theoretically said. The FA's reaction at that point would be jetBlue's first fail.
FA behaves badly, but is not only excused by jetBlue, but their press arm issues falsehoods (incriminating the hated TSA) to cover up that bad behavior. Fail exponentialized (sp? a real word?).
No, not a lot of fault to go around. Pretty much all one place. It would appear.
I count possibly two, the original complainer (which could have been the FA) and Jet Blue. I agree that in this case the TSA responded and the TSA cleared. Both of these actions are part of what they should have done. When I said a lot of fault to spread around, much if not all of it, may end up spread around various Jet Blue actions.
__________________
Livingston's observation of complex systems: The purpose of a system is what it does.
I count possibly two, the original complainer (which could have been the FA) and Jet Blue. I agree that in this case the TSA responded and the TSA cleared. Both of these actions are part of what they should have done. When I said a lot of fault to spread around, much if not all of it, may end up spread around various Jet Blue actions.
Absolutely. Because, corporations are not really people, after all.
Whatever happened, there is likely a lot of fault to go around, none of it on the family (my guess, but I would bet on this one).
Someone will still end up putting fault on the family for not re-boarding the aircraft after they'd been re-cleared, and turning this into a media circus.
Let me be clear: I absolutely disagree with that line of reasoning. But the argument will be made. (Sigh.)
I find much of this discussion misguided because it relies on assuming that details in press reports are correct, but in fact the opposite is true: most details in press reports are wrong. As to infant procedures, I'm not sure what it is on B6, but for other airlines, there is no BP for infants, but rather "infant in arms" is added to one of the parent's BP at the gate.
Someone will still end up putting fault on the family for not re-boarding the aircraft after they'd been re-cleared, and turning this into a media circus.
Let me be clear: I absolutely disagree with that line of reasoning. But the argument will be made. (Sigh.)
I thank the family for doing that. Now we know something interesting and valuable about jetBlue, and now it is more likely that thing will change in the future, for the better.
If it doesn't change, it will be even worse for jetBlue next time. Thanks Riyanna's family, for inconveniencing yourselves for the sake of the rest of us.
That's why a child-in-arms, who's Secure Flight information is not entered into the computer, is more likely to run into this situation.
Birthdate is likely how they quickly determined that the child was not a match to the no-fly or watch list.
Couldn't somebody with some common sense have maybe taken 2 seconds to eye-ball it and see that they were dealing with a damn baby? Somebody screwed up and, sadly, others went along with it.
Programs: UA1K BIS Million Mile Flyer, HH Diamond, IC Plat, SPG Plat, Marriott Silver, Hertz 5*
Posts: 8,177
Quote:
Originally Posted by Mad_Max_Esq
Couldn't somebody with some common sense have maybe taken 2 seconds to eye-ball it and see that they were dealing with a damn baby? Somebody screwed up and, sadly, others went along with it.
I find much of this discussion misguided because it relies on assuming that details in press reports are correct, but in fact the opposite is true: most details in press reports are wrong. As to infant procedures, I'm not sure what it is on B6, but for other airlines, there is no BP for infants, but rather "infant in arms" is added to one of the parent's BP at the gate.
Quote:
Originally Posted by LarryJ
That's why a child-in-arms, who's Secure Flight information is not entered into the computer, is more likely to run into this situation.
Birthdate is likely how they quickly determined that the child was not a match to the no-fly or watch list.
Whom do you mean by "they"?
The press reports include written statements by both jetBlue and TSA, which I doubt are "wrong," meaning, we can safely assume they are accurate. (Truthful is another matter ...)
Riyanna's family let us know the infant's unusual first name. I suggest that "Riyanna <whatever>" is not on the no-fly or watch list, I suggest not even close. JetBlue knows that TSA will not call them on this, but TSA has hinted by publicly indicating it is "not investigating." So it is up to us to connect the dots. Unlike most people, I decline to give jetBlue the benefit of the doubt, under all the circumstances (such as, their claim of a "computer glitch").
Last edited by GaryD; May 11, 12 at 11:02 am..
Reason: added remark about "glitch"
Programs: Southwest Rapid Rewards. Tha... that's about it.
Posts: 1,900
Quote:
Originally Posted by InkUnderNails
My suspicion with no evidence or proof beyond human nature: Another passenger panicked upon seeing in a Muslim and said something to the FA. FA has TSA reclear just to be sure. Whatever happened, there is likely a lot of fault to go around, none of it on the family (my guess, but I would bet on this one).
That was my thought on this situation, as well. I guess I can see JetBlue's story as being true, but that's only because I don't know enough hard facts about the way things work.
* Did the infant, as a lap baby, have her own bording pass with her full name, just like an adult? If not, this invalidates JetBlue's story.
* Does JetBlue's computer system actually compare names on the BPs against the entire US No-Fly or Watch List instantly at the moment they are scanned at the gate? If not, this invalidates JetBlue's story.
* If the infant did, in fact, have her own individual BP with her full name on it, did that BP also have SSSS on it to flag her for additional screening at the c/p? If not, something is seriously wrong with JetBlue's reservation system, which is supposed to check all passengers' names against the No-Fly and Watch Lists at time of reservation, and flag those on the Watch List with an SSSS for additional screening.
Quote:
Originally Posted by jkhuggins
Someone will still end up putting fault on the family for not re-boarding the aircraft after they'd been re-cleared, and turning this into a media circus.
Let me be clear: I absolutely disagree with that line of reasoning. But the argument will be made. (Sigh.)
Quote:
Originally Posted by GaryD
I thank the family for doing that. Now we know something interesting and valuable about jetBlue, and now it is more likely that thing will change in the future, for the better.
If it doesn't change, it will be even worse for jetBlue next time. Thanks Riyanna's family, for inconveniencing yourselves for the sake of the rest of us.
I disagree.
This incident was not the family's fault. They are victims in this entire mess.
But I think it was a mistake for them to not board the plane and take the flight. Their rights were violated - they should have stood up for themselves and asserted their rights. Is that not what most FTers encourage people to do when flying? Assert your rights, don't knuckle under and allow violations to go unchallenged.
By not taking the flight, the Nervous Nellies who made the false report - be they flight crew or other pax - got exactly what they wanted: they didn't have to take a flight with Evil Brown Terr'ist People. As with so many things in life, this reminds me of a movie quote:
"Don't give the pr**k the satisfaction." - Clint Eastwood as GySgt Tom Highway in "Heartbreak Ridge"
They did themselves, and anyone else who is victimized like this in the futute, a disservice by not re-boarding and proving to the rest of the people on board the plane that they were never a threat, and had been treated with gross unfairness by the airline and the TSA.
What if Rosa Parks had decided to simply get off the bus and wait for another one?
That was my thought on this situation, as well. I guess I can see JetBlue's story as being true, but that's only because I don't know enough hard facts about the way things work.
* Did the infant, as a lap baby, have her own bording pass with her full name, just like an adult? If not, this invalidates JetBlue's story.
* Does JetBlue's computer system actually compare names on the BPs against the entire US No-Fly or Watch List instantly at the moment they are scanned at the gate? If not, this invalidates JetBlue's story.
* If the infant did, in fact, have her own individual BP with her full name on it, did that BP also have SSSS on it to flag her for additional screening at the c/p? If not, something is seriously wrong with JetBlue's reservation system, which is supposed to check all passengers' names against the No-Fly and Watch Lists at time of reservation, and flag those on the Watch List with an SSSS for additional screening.
It should be simple enough to get answers to these questions, from B6 frequent flyers. There may not be many of them on this particular list, though.
Quote:
I disagree.
This incident was not the family's fault. They are victims in this entire mess.
But I think it was a mistake for them to not board the plane and take the flight. Their rights were violated - they should have stood up for themselves and asserted their rights. Is that not what most FTers encourage people to do when flying? Assert your rights, don't knuckle under and allow violations to go unchallenged.
By not taking the flight, the Nervous Nellies who made the false report - be they flight crew or other pax - got exactly what they wanted: they didn't have to take a flight with Evil Brown Terr'ist People. As with so many things in life, this reminds me of a movie quote:
"Don't give the pr**k the satisfaction." - Clint Eastwood as GySgt Tom Highway in "Heartbreak Ridge"
They did themselves, and anyone else who is victimized like this in the futute, a disservice by not re-boarding and proving to the rest of the people on board the plane that they were never a threat, and had been treated with gross unfairness by the airline and the TSA.
What if Rosa Parks had decided to simply get off the bus and wait for another one?
I see your point, but I think in this case, they made a calculated decision to publicize the problem, by voluntarily giving up even more rights than had already been taken from them. The point, and the "proof," has been far more widely publicized now, than it would have been I think, including JetBlue's public apology and implied public assurance that they were never a threat.
Maybe Riyanna should have refused to get off the plane. Honestly. But, meekly returning after the humiliation of her whole family was not clearly the best course to take here. YMMD
Location: Finally back in Boston after escaping from New York
Posts: 11,349
Quote:
Originally Posted by InkUnderNails
My suspicion with no evidence or proof beyond human nature: Another passenger panicked upon seeing in a Muslim and said something to the FA. FA has TSA reclear just to be sure. Whatever happened, there is likely a lot of fault to go around, none of it on the family (my guess, but I would bet on this one).
My suspicions (with the same lack of evidence) are that your suspicions are correct.
JetBlue is now blaming the incident on computer error:
Quote:
Upon boarding Flight 510 at Fort Lauderdale International Airport on Tuesday evening, a customer’s boarding pass was flagged in our system as being on the No Fly list. We notified and collaborated with TSA. TSA cleared the customers to travel on JetBlue.
We are investigating this particular incident. We believe this was a computer glitch. Our crewmembers followed the appropriate protocols, and we apologize to the family involved in this unfortunate circumstance.
JetBlue takes all security concerns very seriously and the safety of all of our customers and crewmembers is our number one priority. There are layers of security checkpoints in place — from booking a flight to checking-in, clearing security and boarding an aircraft – that are enforced by the airline in collaboration with airport authorities and the Transportation Security Administration to ensure all customers enjoy a safe and secure travel experience. Our crewmembers are trained to address each situation discreetly, treating every customer with dignity and respect.
How could anyone think a baby would be on the no fly or watch lists? Hard to believe there wasn't even ONE person who questioned this? I guess common sense is against the rules.
