Aviation News, Headlines & Alerts
 
George Hatcher's Air Flight Disaster

Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

GOL – NTSB Report September 29, 2006

DCA06RA076A
On September 29, 2006, at approximately 4:57 pm, Brasilia standard time, a midair collision occurred over the Brazilian Amazon jungle, between a Boeing 737-800 (PR-GTD) operated by Gol Airlines of Brazil, and an Embraer Legacy 600 business jet (N600XL) owned and operated by Excelaire of Long Island, New York.
The accident investigation is being conducted under the authority of the Brazilian Aeronautical Accident Prevention and Investigation Center (DIPAA). Under the provisions of ICAO Annex 13, the United States, as state of registry and operator of the Excelaire Legacy, and state of manufacture of the Boeing 737 and Honeywell avionics equipment in both airplanes, has provided an accredited representative and technical advisors for the investigation. The U.S. team included the accredited representative from the major aviation accident investigations division of the NTSB, as well as technical advisors in operations, systems, air traffic control, flight recorders, and aircraft performance. Additional technical advisors from Boeing, Excelaire, Honeywell, and FAA have also been included.

The Boeing 737 was destroyed by in-flight breakup and impact forces; all 154 occupants were fatally injured. The wreckage of the 737 was located in remote jungle terrain with very difficult access. Brazilian military search and rescue personnel located the flight recorders and all significant portions of the wreckage except the outer portion of the left wing. The Legacy N600XL experienced damage to its left wing and left horizontal stabilizer and performed an emergency landing at the Cachimbo Air Base, approximately 100 miles northwest of the collision site. There was no further damage to the airplane, and the 2 crew members and 5 passengers were not injured. The airplane remained at the base and significant components have been tested and recovered from the aircraft.

Visual meteorological conditions prevailed in the area of the accident. Both aircraft were operating under instrument flight rules, on instrument flight plans and clearances. The Boeing 737 was a scheduled domestic air carrier flight enroute from the Eduardo Gomes International Airport, Manaus, Brazil; to the Presidente Juscelino Kubitschek Airport, Brasilia. The Legacy N600XL was enroute from the Prof. Urbano Ernesto Stumpf airport, San Jose dos Campos, Brazil (SBSJ), to a stopover in Manaus, and eventually enroute back to the U.S. This was Excelaire’s initial flight with this aircraft, taking delivery from the Embraer factory and a planned flight to Excelaire’s home base in New York.

The Legacy N600XL departed SBSJ at about 2:51 pm. The filed flight plan included a routing via the OREN departure procedure to Pocos beacon, then airway UW2 to Brasilia VOR (BRS), airway UZ6 to Manaus. The cruise altitude was filed as FL370, with a planned change to FL360 at BRS, and to FL380 at the TERES navigational fix, approximately 282 miles north of BRS.

After takeoff, N600XL was issued a number of interim altitudes during climb, all of which were read back. The flight was cleared to proceed direct to Araxa VOR (on airway UW2), and at 3:11 pm was cleared to climb to FL370. At 3:33 pm, the airplane leveled at FL370.

At 3:35 pm, the Boeing 737 departed Eduardo Gomes airport, requesting FL370 as a cruise altitude, and a routing via UZ6 to BRS. The airplane reached FL370 at 3:58 pm. There were no anomalies in communications with or radar surveillance of the Boeing 737 throughout the flight.

At 3:51 pm, an air traffic controller in the Brasilia ACC (CINDACTA 1) instructed N600XL to change frequencies to the next controller’s sector. The crew of N600XL reported in on the assigned frequency that the flight was level at FL370. ATC acknowledged and instructed the crew to “ident” (flash their transponder). Radar indicates that the ident was observed. This was the last two-way communication between N600XL and ATC. At this time the airplane was approximately 40 nautical miles south of BRS.

At 3:56pm the Legacy N600XL passed BRS level at FL370. There is no record of a request from N600XL to the control agencies to conduct a change of altitude, after reaching flight level 370. The crew made calls, but there is no communication in which they requested a change of flight level. There is also no record of any instruction from air traffic controllers at Brasilia Center to the aircraft, directing a change of altitude.

When the airplane was about 30 miles north-northwest of BRS, at 4:02 pm, the transponder of N600XL was no longer being received by ATC radar. A transponder reports a unique code, aiding radar identification, and provides an accurate indication of the airplane’s altitude. Additionally, the transponder is a required component for the operation of Traffic Collision Avoidance System equipment, commonly called the TCAS system.

Between 3:51 pm and 4:26 pm, there were no attempts to establish radio communications from either the crew of N600XL or ATC. At 4:26 pm the CINDACTA 1 controller made a “blind call” to N600XL. Subsequently until 4:53 pm, the controller made an additional 6 radio calls attempting to establish contact. The 4:53 call instructed the crew to change to frequencies 123.32 or 126.45. No replies were received.

There is no indication that the crew of N600XL performed any abnormal maneuvers during the flight. Flight Data Recorder information indicates that the airplane was level at FL370, on course along UZ6, and at a steady speed, until the collision. Primary (non-transponder) radar returns were received corresponding to the estimated position of N600XL until about 4:30 pm. For 2 minutes, no returns were received, then returns reappeared until 4:38 pm. After that time, radar returns were sporadic.

Beginning at 4:48 pm, the crew of N600XL made a series of 12 radio calls to ATC attempting to make contact. At 4:53, the crew heard the call instructing them to change frequencies, but the pilot did not understand all of the digits, and requested a repeat. No reply from ATC was received. The pilot made 7 more attempts to establish contact. At 4:56:54 pm the collision occurred at FL370, at a point about 460 nautical miles north-northwest of BRS, on airway UZ6.

There was no indication of any TCAS alert on board either airplane, no evidence of pre-collision visual acquisition by any flight crew member on either aircraft, and no evidence of evasive action by either crew.

Wreckage and damage examination indicates that it is likely the left winglet of the Legacy (which includes a metal spar) contacted the left wing leading edge of the Boeing 737. The impact resulted in damage to a major portion of the left wing structure and lower skin, causing the outer portion of the wing to fail in an upward direction, separating the outer portion of the wing and a significant portion of additional upper wing skin, ultimately rendering the 737 uncontrollable. Flight recorder information ceased at an approximate altitude of 7,887 feet.

After the collision, the crew of N600XL made numerous further calls to ATC declaring an emergency and their intent to make a landing at the Cachimbo air base. At 5:02 pm, the transponder returns from N600XL were received by ATC.

At 5:13 pm, an uninvolved flight crew assisted in relaying communications between N600XL and ATC until the airplane established communication with Cachimbo tower.

Flight recorders from both airplanes were recovered and downloaded at the Transportation Safety Board of Canada (TSB) laboratories. Transcriptions of the cockpit voice recorders (CVRs) were prepared (the transcript of the Legacy’s CVR was produced at the NTSB’s laboratory in Washington, D.C.) and data from flight data recorders obtained.

Initial interviews and medical examinations were conducted with the crew of the Legacy. Air Traffic Control data was gathered. Preliminary tests of the avionics equipment on the Legacy were performed. Wreckage of the 737 was examined.

Additional investigative work will include laboratory tests of the avionics components removed from the Legacy, an examination of the operating procedures of the avionics, interviews with ATC personnel, examination of ATC practices and comparison between Brazilian and FAA procedures, a technical examination of ATC communication and surveillance systems, and further examination of the training provided to the operators.

Brazilian Contact: Brazilian Aeronautical Accident Prevention& Investigation Center 55-61-3329-9160

src: NTSB Final




‘Guaranteed to see the eclipse’: A plane might be the best place to see the phenomenon

‘Guaranteed to see the eclipse’: A plane might be the best place to see the phenomenon
According to a physicist and astronomer, seeing the eclipse from a plane comes with some benefits and a few challenges.

Read More




The Twin-Engined Piston Beechcraft Plane: A Guide To The Beechcraft Baron

The Twin-Engined Piston Beechcraft Plane: A Guide To The Beechcraft Baron
Let’s take a deep dive into the characteristics of one of Beechract’s flagship aircraft, the Baron.

Read More




EVA Air plane enrooted London makes emergency landing after onboard passenger attempts suicide

EVA Air plane enrooted London makes emergency landing after onboard passenger attempts suicide
Details regarding the passenger’s identity and the underlying reasons for the attempted suicide remain undisclosed. However, onboard crew members, assisted by a physician among the passengers, administered initial medical assistance to the individual

Read More




Older Boeing Plane Found to Have Missing Panel After Flight From California to Oregon

Older Boeing Plane Found to Have Missing Panel After Flight From California to Oregon
A post-flight inspection revealed a missing panel on an older Boeing 737-800 that had just arrived at its destination in southern Oregon on Friday after

Read More




Alaska Airlines Boeing 737 windshield cracks while landing at Portland

Alaska Airlines Boeing 737 windshield cracks while landing at Portland
An Alaska Airlines flight from Washington D.C. to Portland, Oregon suffered a cracked windshield, with 159 passengers and 6 crew onboard. Despite the crack the crew of the Boeing 737 landed safely.

Read More




Lufthansa plane makes emergency landing in Greece after smoke in cabin

Lufthansa plane makes emergency landing in Greece after smoke in cabin
A Lufthansa flight with 190 passengers on board made an emergency landing Monday in Rhodes after reporting smoke in the cabin, according to the operator of Greek regional airports, Fraport.

Read More




8 Incidents in 2 Weeks: What’s Going on With United’s Planes?

8 Incidents in 2 Weeks: What’s Going on With United’s Planes?
While no one was injured, most of the mishaps required emergency landings or diversions. One safety expert said the incidents were not the result of “systemic problems.”

Read More




2 fallen NY National Guard members get plane-side honors

2 fallen NY National Guard members get plane-side honors
In Latham, the governor honored upstate natives Casey Frankoski and John Grassia who gave the ultimate sacrifice.

Read More




Lufthansa flight to Dubai makes emergency landing in Rhodes | eKathimerini.com

Lufthansa flight to Dubai makes emergency landing in Rhodes | eKathimerini.com
A Lufthansa flight from Frankfurt to Dubai has been diverted to Rhodes where it landed just before 6 p.m. Monday.

Read More




Shamiso Mosaka: South African TV star removed from CemAir plane for ‘unruly’ behaviour

Shamiso Mosaka: South African TV star removed from CemAir plane for ‘unruly’ behaviour
Shamiso Mosaka was removed from a flight by police officers after crew said she was being “abusive”.

Read More




Redispatching: The Intricate Rule That Optimizes Long-Haul Airline Flight Planning

Redispatching: The Intricate Rule That Optimizes Long-Haul Airline Flight Planning
International airlines often do not file the marketed destination as their flight plan destination. Here’s how and why a “redispatch” works.

Read More




Gila Bend Municipal Airport plane crash kills 1, injures another

Gila Bend Municipal Airport plane crash kills 1, injures another
Articles and videos about Gila Bend Municipal Airport plane crash kills 1, injures another on FOX 10 Phoenix.

Read More




Hope to solve MH370 mystery after underwater search expert vows to find plane

Hope to solve MH370 mystery after underwater search expert vows to find plane
US-based Deep Sea Vision, which claimed to have found Amelia Earhart’s long lost plane on the Pacific Ocean floor, says it will a use craft called a Hugin 6000 to hunt for the missing MH370 plane

Read More




1 person dead and 1 injured after plane crash in Gila Bend

1 person dead and 1 injured after plane crash in Gila Bend
One person is dead and another is in serious condition following a small plane crash near Gila River Municipal Airport.

Read More




Officials investigating Gila Bend plane crash that killed 1, injured another

Officials investigating Gila Bend plane crash that killed 1, injured another
One person died and another was injured following a plane crash Sunday morning at Gila Bend Municipal Airport.

Read More




Fresh hope to solve the MH370 mystery after expert vows to find wreckage

Fresh hope to solve the MH370 mystery after expert vows to find wreckage
A DEEP sea exploration company has promised to send a state-of-the-art underwater drone to the bottom of the sea to finally solve the MH370 mystery. Over a decade ago, the Malaysian Airlines flight…

Read More




Reba McEntire Honors Band Members 33 Years After Fatal Plane Crash, “Rest in Peace, My Friends”

Reba McEntire Honors Band Members 33 Years After Fatal Plane Crash, “Rest in Peace, My Friends”
Reba McEntire remembered her former bandmates and tour manager on the anniversary of the fatal plane crash that took their lives.

Read More




Content not attributed to or linked to original, is the property of AirFlightDisaster.com; all rights reserved.

Site Credits