Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Chill out Delta!

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
Thankfully no one waiting on the taxiway huh. That make it ok? Sure had an emergency, but one should land between the white lights, not the blue lights. Just saying. :erm:

Supposedly, work had been done overnight and someone screwed up and put white lights on that taxiway.... supposedly. But it was a nice job backing things up with the ILS/FMS....:blush:
 
OMG, an IP with FP in the JS! Somehow, I fail to believe he was in the cockpit at the time of the incident.
 
A medical emergency at 5am with a slam dunk visual approach to the inboard in a 767, and a checkairman puking in the jumpseat with food poising?

The combined occurrence of a slam dunk with a sick pax on board is enough overload for a Delta pilot to lose their SA composure? Oh wait... your caveat that it was a 767 and not some RJ toy makes it so much more perilous?
 
A medical emergency at 5am with a slam dunk visual approach to the inboard in a 767, and a checkairman puking in the jumpseat with food poising?

Details are sketchy, and it seems no one really wants to divulge EXACTLY WHEN the guy got sick.

But he was p1ssing out his a$$hole/puking. There WASN'T a woman going into labor, there WASN'T a passenger going into cardiac arrest. The crew elected to continue the flight.

Lesson for me: don't make your own emergency trying to rush an abnormal.

Good point. And IIRC, they accepted the runway change when ATL was "switching the airport around"

Then they accepted the sidestep.

If one was up all night 10 hours without an IRO break, in a declared "emergency", why not just stick with the originally briefed/planned/FMS loaded procedure?

You're in an emergency for Christ's sake, ATC is working for YOU, you're NOT working for them.
 
A medical emergency at 5am with a slam dunk visual approach to the inboard in a 767, and a checkairman puking in the jumpseat with food poising?

Ummmm, nope. They screwed the pooch. Maybe the jumpseater had one too many sundaes like el general.
 
Ummmm, nope. They screwed the pooch. Maybe the jumpseater had one too many sundaes like el general.

No jumpseater, a check airman who was part of the crew got sick a couple hours into the northbound flight. They elected to continue, but no breaks for the 9+ hour flight. Not a good outcome obviously.



Bye Bye---General Lee
 
No jumpseater, a check airman who was part of the crew got sick a couple hours into the northbound flight. They elected to continue, but no breaks for the 9+ hour flight. Not a good outcome obviously.



Bye Bye---General Lee

Lemme guess...you were non-reving on this flight because first class was open, and you had to pad your miles flown so far for the year?
 
So, how was this unfortunate incident kept from the media (I think that's the case), and what were the consequences, and remedial steps taken on the part of the crew?
The "Captain Happy" thing sure hit CNN pretty quick, probably released by someone with a bone to pick (ATC?), yet the more serious taxiway landing didn't have the same coverage.
If it had been a regional airline I believe the outcome would have been quite different.
Mistakes are made, we are humans, and we learn and modify our procedures to prevent reoccurrence. The full facts of incidences such as this must be released, just like the Buffalo crash, so we can all learn from them.
 
So, how was this unfortunate incident kept from the media (I think that's the case), and what were the consequences, and remedial steps taken on the part of the crew?

It happened not too far from the infamous NWA crew that was "arguing over a new scheduling software" while they overflew their destination. So the media was consumed with that issue.

It was ASAP'd by the DAL crew, not sure if there was any retraining involved.

If it had been a regional airline I believe the outcome would have been quite different.

Sad, but true. Had it been a regional crew that talked to the controller like that, the "experts" would have ranted and raved about how unprofessional regional pilots are.

Mistakes are made, we are humans, and we learn and modify our procedures to prevent reoccurrence. The full facts of incidences such as this must be released, just like the Buffalo crash, so we can all learn from them.

Again, a true statement. AGAIN, the view of the "experts" is that since it was legacy crew and there was no bent metal or a body count, it's perceived as OK. Because, again, they're legacy pilots. They're allowed to do such things.

The same point stands, had it been a regional crew, we would never hear the end of it. Just like CAL crew that landed on taxi way Zulu in EWR, the UAL crew that almost hit mountain, the AA crew that almost stalled an Airbus going into holding. Legacy pilots are held to a different/more forgiving standard when they completely fukc something up..........
 

Latest resources

Back
Top