The strange reasons why United pilots declare emergencies
Thread Starter
Join Date: Apr 2008
Location: nowhere
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
The strange reasons why United pilots declare emergencies
Occurrence No.: A16A0077 Occurrence Type: INCIDENT REPORTABLE
Class: CLASS 5 Reportable Type: SMOKE OR FIRE (iii)
Date: 2016-08-16 Time: 02:52:00 UTC
Region of Responsibility:
ATLANTIC
Location: 580.00 Nautical miles E From CYQX - GANDER INTL - GANDER
Country: CANADA Ocean: NORTH ATLANTIC OCEAN
Ground Injuries: Fatal: 0 Minor: 0
Serious: 0 Unknown: 0
---------- Aircraft 1 ---------
Registration: N781UA Operator: UNITED AIRLINES
Manufacturer: BOEING Operator Type: COMMERCIAL
Model: 777-200 CARS Sub Part: 701 - FOREIGN
Injuries: Fatal: 0 Minor: 0
Serious: 0 None: 246
Unknown: 0
Occurrence Summary:
N781UA, a Boeing 777-200 aircraft operated by United Airlines, was conducting flight UAL999 from Newark/Liberty Intl, NJ (KEWR) to Brussels, Belgium (EBBR). When in cruise flight at FL380 and approximately 580 nautical miles East of Gander Intl, NL (CYQX), a flight attendant reported fumes to the flight crew. It was determined that the odour was contained to the first class inboard lavatory. The flight crew decided to don their oxygen masks and requested a diversion to CYQX. Due to traffic, ATC was unable to provide a clearance. The crew elected to declare an emergency and deviated without a clearance in accordance with in-flight contingency procedures. Once level at FL300, the flight received a clearance for CYQX where it landed without further incident or reported injuries.
Maintenance personnel found no evidence of smoke or heat, and determined that the trash container was the source of the odour.
Occurrence No.: A16A0081 Occurrence Type: INCIDENT REPORTABLE
Class: CLASS 5 Reportable Type: EMERGENCY/PRIORITY (xi)
Date: 2016-08-19 Time: 01:32:00 UTC
Region of Responsibility:
ATLANTIC
Location: 370.00 Nautical miles E From CYQX - GANDER INTL - GANDER
Country: CANADA Ocean: NORTH ATLANTIC OCEAN
Ground Injuries: Fatal: 0 Minor: 0
Serious: 0 Unknown: 0
---------- Aircraft 1 ---------
Registration: N673UA Operator: UNITED AIRLINES
Manufacturer: BOEING Operator Type: COMMERCIAL
Model: 767-300 CARS Sub Part: 701 - FOREIGN
Injuries: Fatal: 0 Minor: 0
Serious: 0 None: 190
Unknown: 0
Occurrence Summary:
N673UA, a Boeing 767-322 aircraft operated by United Airlines, was conducting flight UAL30 from Newark/Liberty Intl, NJ (KEWR) to Munich/Franz Josef Strauss Intl, Germany (EDDM). During cruise flight in the vicinity of 46N050W, the crew selected the flight management computer to provide a course offset to the right; however, the aircraft began to deviate to the left. The crew was unable to correct using the flight management computer, and selecting the backup routing also introduced an error. The crew requested a clearance to return to KEWR due to navigational problems but due to traffic, ATC was unable to provide the request. The crew elected to declare an emergency and deviated without a clearance in accordance with in-flight contingency procedures. Once level at FL300, the flight received a clearance to return to KEWR where a landing was made without further incident.
The operator’s maintenance found that the right High Frequency Transceiver had failed, and proceeded to replace it. All subsequent checks were accomplished and no further discrepancies were noted.
Class: CLASS 5 Reportable Type: SMOKE OR FIRE (iii)
Date: 2016-08-16 Time: 02:52:00 UTC
Region of Responsibility:
ATLANTIC
Location: 580.00 Nautical miles E From CYQX - GANDER INTL - GANDER
Country: CANADA Ocean: NORTH ATLANTIC OCEAN
Ground Injuries: Fatal: 0 Minor: 0
Serious: 0 Unknown: 0
---------- Aircraft 1 ---------
Registration: N781UA Operator: UNITED AIRLINES
Manufacturer: BOEING Operator Type: COMMERCIAL
Model: 777-200 CARS Sub Part: 701 - FOREIGN
Injuries: Fatal: 0 Minor: 0
Serious: 0 None: 246
Unknown: 0
Occurrence Summary:
N781UA, a Boeing 777-200 aircraft operated by United Airlines, was conducting flight UAL999 from Newark/Liberty Intl, NJ (KEWR) to Brussels, Belgium (EBBR). When in cruise flight at FL380 and approximately 580 nautical miles East of Gander Intl, NL (CYQX), a flight attendant reported fumes to the flight crew. It was determined that the odour was contained to the first class inboard lavatory. The flight crew decided to don their oxygen masks and requested a diversion to CYQX. Due to traffic, ATC was unable to provide a clearance. The crew elected to declare an emergency and deviated without a clearance in accordance with in-flight contingency procedures. Once level at FL300, the flight received a clearance for CYQX where it landed without further incident or reported injuries.
Maintenance personnel found no evidence of smoke or heat, and determined that the trash container was the source of the odour.
Occurrence No.: A16A0081 Occurrence Type: INCIDENT REPORTABLE
Class: CLASS 5 Reportable Type: EMERGENCY/PRIORITY (xi)
Date: 2016-08-19 Time: 01:32:00 UTC
Region of Responsibility:
ATLANTIC
Location: 370.00 Nautical miles E From CYQX - GANDER INTL - GANDER
Country: CANADA Ocean: NORTH ATLANTIC OCEAN
Ground Injuries: Fatal: 0 Minor: 0
Serious: 0 Unknown: 0
---------- Aircraft 1 ---------
Registration: N673UA Operator: UNITED AIRLINES
Manufacturer: BOEING Operator Type: COMMERCIAL
Model: 767-300 CARS Sub Part: 701 - FOREIGN
Injuries: Fatal: 0 Minor: 0
Serious: 0 None: 190
Unknown: 0
Occurrence Summary:
N673UA, a Boeing 767-322 aircraft operated by United Airlines, was conducting flight UAL30 from Newark/Liberty Intl, NJ (KEWR) to Munich/Franz Josef Strauss Intl, Germany (EDDM). During cruise flight in the vicinity of 46N050W, the crew selected the flight management computer to provide a course offset to the right; however, the aircraft began to deviate to the left. The crew was unable to correct using the flight management computer, and selecting the backup routing also introduced an error. The crew requested a clearance to return to KEWR due to navigational problems but due to traffic, ATC was unable to provide the request. The crew elected to declare an emergency and deviated without a clearance in accordance with in-flight contingency procedures. Once level at FL300, the flight received a clearance to return to KEWR where a landing was made without further incident.
The operator’s maintenance found that the right High Frequency Transceiver had failed, and proceeded to replace it. All subsequent checks were accomplished and no further discrepancies were noted.
@ underfire...
You forgot Gander's role on September 11th 2001... Over 6500 passengers were stranded there on that one day.
That is like the most PAX Gander has ever had!
What happened to Bangor, avoiding FAA scutiny?
What happened to Bangor, avoiding FAA scutiny?
Don't see what's 'strange' about their declaration (s)
Better to declare an emergency in those situations to provide maximum assistance, flexibility and co-operation from ATC
Perfectly legitimate and probably called for by SOP.
Better to declare an emergency in those situations to provide maximum assistance, flexibility and co-operation from ATC
Perfectly legitimate and probably called for by SOP.
Join Date: Apr 2003
Location: holding short of....
Posts: 24
Likes: 0
Received 0 Likes
on
0 Posts
Safety First...
First of all Safety first... well done for the crew that as a team worked together in a profesional way. The cabin crew communicated straight away to the flight deck, who reacted and acted according to their instincts and situational awareness (sensing abnormal burning smell, running out of options if the situation would have worsen). Pure CRM.
I do not get the title of this topic... Sounds a bit anti CRM or macho-tic...... the words STRANGE REASONS under my first impression sound degrading to the professional crew that did a safe job. When you get a fire... it is already too late... better to buy as much time as possible.
Second of all... I always like to teach my students using the example about the crew of the UPS Flight 1307 that landed at Philly seconds to be destroyed by an inflight cargo fire.
If you read about it, it all started with a strange strong odor and ended up with a destroyed plane and luckily no fatalities.
The crew reacted to their senses, they already started working on their plan well before the alarm-indication warned them of a serious problem (cargo fire).
It all started with the First Officer sensing a strange strong odor... the Captain and the FE took this so serious that they did not dismiss it, they worked on it as a team.
If they wouldn't have done it... today the report would have included 3 fatalities on board plus many on ground...
http://www.ntsb.gov/news/events/Page...nsylvania.aspx
Whatever sounds strange while you are in your sofa with your laptop, it makes perfect sense if you are seated in the flightdeck over the Atlantic....
I do not get the title of this topic... Sounds a bit anti CRM or macho-tic...... the words STRANGE REASONS under my first impression sound degrading to the professional crew that did a safe job. When you get a fire... it is already too late... better to buy as much time as possible.
Second of all... I always like to teach my students using the example about the crew of the UPS Flight 1307 that landed at Philly seconds to be destroyed by an inflight cargo fire.
If you read about it, it all started with a strange strong odor and ended up with a destroyed plane and luckily no fatalities.
The crew reacted to their senses, they already started working on their plan well before the alarm-indication warned them of a serious problem (cargo fire).
It all started with the First Officer sensing a strange strong odor... the Captain and the FE took this so serious that they did not dismiss it, they worked on it as a team.
If they wouldn't have done it... today the report would have included 3 fatalities on board plus many on ground...
http://www.ntsb.gov/news/events/Page...nsylvania.aspx
Whatever sounds strange while you are in your sofa with your laptop, it makes perfect sense if you are seated in the flightdeck over the Atlantic....
Join Date: Aug 2005
Location: fairly close to the colonial capitol
Age: 55
Posts: 1,693
Likes: 0
Received 0 Likes
on
0 Posts
I too fail to see the problem here, other than perhaps a slight left hand way of getting back to EWR (a maintenance hub) for the NAV issue once ATC claimed they were unable.
Join Date: Mar 2001
Location: Either the back of a sim, or wherever Crewing send me.
Posts: 1,031
Likes: 0
Received 1 Like
on
1 Post
With the possibility of a fire developing whilst well out over the North Atlantic, would you not have declared an emergency given that ATC weren't giving you what you wanted/needed. Every second counts, I suggest that this is a very good reason to declare an emergency, which is a requirement if you are going to perform a contingency manoeuvre.
A navigation issue again over the Atlantic, sounds to me like a good decision, and again if ATC can't give you what you need you do what you have to do.
At the end of the day these 2 sets of crew made effective timely decisions, and then acted on them without further delay. Too many times in the past we have read about crews pressing on or dilly dallying and the situation ending up unpleasantly.
A navigation issue again over the Atlantic, sounds to me like a good decision, and again if ATC can't give you what you need you do what you have to do.
At the end of the day these 2 sets of crew made effective timely decisions, and then acted on them without further delay. Too many times in the past we have read about crews pressing on or dilly dallying and the situation ending up unpleasantly.
Last edited by Johnny F@rt Pants; 22nd Sep 2016 at 06:32. Reason: Typo
Thread Starter
Join Date: Apr 2008
Location: nowhere
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
Admittedly, the trash bin odour pilots were in a difficult situation if they have a report of fumes from the first class lav and their procedures are that they are not allowed to leave the flight deck for security reasons. Not all the FA's are the sharpest of people. I worked at an airline that had smoke coming from the galley and the reports enough to cause an emergency evacuation. Turns out that there were muffins burning in the oven.
Join Date: Jun 1999
Location: world
Posts: 3,424
Likes: 0
Received 0 Likes
on
0 Posts
JammedStab, if you are the type who is going to plod on regardless, please do me a favour and let me know who you fly for so that I can avoid using your airline in case it's you sitting at the pointy end!
Please let me know which airline you fly for Jammed?
If you think it is strange to divert from the middle of the Atlantic with a possible fire on board, I don't want to fly with you !
If you think it is strange to divert from the middle of the Atlantic with a possible fire on board, I don't want to fly with you !
Cost of loss of a hull and 250 passengers: easily 500 million
Cost of an emergency diversion: perhaps 50,000?
So in purely financial terms you should be able to justify several thousand false alarms for each true alarm.
Cost of an emergency diversion: perhaps 50,000?
So in purely financial terms you should be able to justify several thousand false alarms for each true alarm.
Join Date: Feb 2015
Location: New Hampshire
Posts: 152
Likes: 0
Received 0 Likes
on
0 Posts
The central purpose of the in-flight investigation would be to find the fire and discover what is needed to put it out.
BTW: I also vote that declaring an emergency in these situations is appropriate. I don't doubt that the navigational issue could have been diagnosed in flight, but how much "experimentation" do you tolerate before declaring the issue a serious matter for the ground personnel to resolve? I would hope with an ATC flight, not a lot.
N673UA, a Boeing 767-322 aircraft operated by United Airlines, was conducting flight UAL30 from Newark/Liberty Intl, NJ (KEWR) to Munich/Franz Josef Strauss Intl, Germany (EDDM). During cruise flight in the vicinity of 46N050W, the crew selected the flight management computer to provide a course offset to the right; however, the aircraft began to deviate to the left. The crew was unable to correct using the flight management computer, and selecting the backup routing also introduced an error. The crew requested a clearance to return to KEWR due to navigational problems but due to traffic, ATC was unable to provide the request. The crew elected to declare an emergency and deviated without a clearance in accordance with in-flight contingency procedures. Once level at FL300, the flight received a clearance to return to KEWR where a landing was made without further incident.
The operator’s maintenance found that the right High Frequency Transceiver had failed, and proceeded to replace it. All subsequent checks were accomplished and no further discrepancies were noted.
The operator’s maintenance found that the right High Frequency Transceiver had failed, and proceeded to replace it. All subsequent checks were accomplished and no further discrepancies were noted.
I am aware that some other B767 operators have problems with their FMC dumping data when the crew try to enter the SLOP at the start of the Oceanic leg, including the alternate FPLN. The manufacturer's advice was to leave 5 minutes between starting the leg and entering the offset, but that doesn't work either. The pilot I spoke to said crews were using heading hold while they manually entered the remainder of their route into the system. Painful, but less so than a MAYDAY and diversion?