Plane crash map Locate crash sites, wreckage and more

N691TA accident description

Florida map... Florida list
Crash location Unknown
Nearest city Jacksonville, FL
30.332184°N, 81.655651°W
Tail number N691TA
Accident date 28 Nov 2005
Aircraft type Raytheon Corporate Jets Beechjet 400
Additional details: None

NTSB Factual Report

HISTORY OF FLIGHT

On November 28, 2005, about 1340 eastern standard time, a Raytheon Beechcraft 400A, N691TA, lost all power from both of the Pratt & Whitney Canada (PWC) JT15D-5 engines while descending from flight level (FL) 380 (approximately 38,000 feet above sea level) near Jacksonville, Florida. The two pilots on board were not injured. The airplane safely landed at Jacksonville International Airport. The flight was operated by Flight Options in visual meteorological conditions on an instrument flight rules flight plan under the provisions of 14 Code of Federal Regulations Part 91 from Indianapolis, Indiana, to Marco Island, Florida.

The captain was seated in the right seat and was performing check airman and pilot monitoring duties. The first officer was seated in the left seat and was the pilot flying. The flight crew reported that after departing Indianapolis, it took approximately 25 minutes to climb to FL350 where they remained for about 40 minutes. The airplane then climbed to FL400 where it remained for about 30 minutes. At about 1316, air traffic control (ATC) cleared the flight to descend to FL380. The crew did so, and they flew level at that altitude for about 15 minutes. At 1331, ATC cleared the crew to descend at pilot's discretion to FL330, the crew delayed descent briefly until the planned top of descent point. The pilots reported that they were cruising in visual meteorological conditions at the time, near cloud tops. They reported the static air temperature was -57º Celsius and the total air temperature was -37º Celsius. The crew monitored fuel temperatures during the flight and noted a minimum of -23º to -24º degrees Celsius. The captain remembered looking outside for signs of airframe ice, and saw none. They were not operating engine anti-ice. The pilots reported that they had been cruising at about .73 to .74 Mach, and there were no abnormal indications throughout the flight.

The pilots reported that when retarding the throttles to initiate the descent, they heard a loud pop from the right engine followed about 10 seconds later by a loud pop from the left engine. The captain also termed the sound a "bang" and said he had heard a compressor stall at another time in a Beechjet, on the ground, and this sound was not similar. The pilots observed the engine indicators quickly roll back, N2 dropped immediately to 46% and then to zero. The pilots donned their oxygen masks and declared an emergency and advised ATC that they had lost both engines and needed to descend to a lower altitude. The captain said he purposely switched electrical power to the emergency battery bus to save the battery charge for an attempted restart.

The captain said there was brief loss of airspeed indication, and he said he used the "peanut" (backup) gyro attitude indicator and altimeter to control airplane pitch. About one to one and a half minutes later the airspeed indication returned to normal. (The captain stated he knew of a service bulletin that was related to this phenomenon.)

After both engines flamed out, the crew set the airspeed for 170 to 180 knots for best glide. The captain planned on attempting a battery start at 180 knots, per the restart envelope on the emergency checklists. When he first attempted to restart the left engine using the battery-assisted restart procedure at about FL280, he did not observe any rotation, the voltage dropped from 28 volts to 8 volts, and he heard a "humming or groaning" sound. As the airplane passed through FL260 he reported that he pitched further downward to increase speed to 230 knots and to attempt an air start of both engines, but he did not observe any N2 rotation on either engine and the attempt was aborted. The crew then switched back to normal battery to attempt a battery-assisted restart on the right engine, with no success.

During the descent, ATC provided vectors to the ILS [instrument landing system] approach to runway 7 at Jacksonville. The flight was in clouds during the descent, with moderate to heavy rain beginning at about 10,000 feet. As the airplane neared the airport, ATC provided continuous callouts of the distance remaining to the runway that the pilots later stated was very helpful in managing their descent and approach to the airport. The captain took over the controls at about 9,000 feet for the landing. The crew manually extended the landing gear and broke out of the clouds at about 1,200 feet. The pilots stated that at about 500 feet, they began to observe N2 indications between 1% and 2%. When on short final, they saw the left engine N1 indicate 1.1%.

After they landed and rolled off the runway onto a taxiway, the right landing gear tire deflated. The pilots stated that while the airplane was stopped on the taxiway after the airplane had landed and they were waiting to be towed into the ramp, they pressed the left engine starter button and noted engine rotation on the cockpit gauges but aborted the start. The captain stated that the engine would rotate, but "wouldn't take." Instruments indicated 24 volts on the battery, and a positive fuel flow, but no rise in turbine inlet temperature.

Post-event examination revealed that the fuel gauges indicated 1400 and 1350 pounds of fuel in the left and right wing tanks, respectively, and visual examination noted fuel level up to the flapper valves in each tank. The center tank was empty.

PERSONNEL INFORMATION

The captain held an airline transport pilot certificate and had approximately 8,200 hours total time, with 1,800 hours in the Beechjet 400A. The first officer held an airline transport pilot certificate, and had approximately 3,100 hours total time, with about 20 hours in the Beechjet 400A. The first officer was newly hired by Flight Options and was receiving Initial Operating Experience training from the captain during the incident flight.

AIRCRAFT INFORMATION

According to Flight Options maintenance records, the airplane, fuselage serial number (SN) RK-317, had operated 4,010.3 hours and 3,359 cycles since new. The airplane underwent an "A" check on November 15, 2005, and had operated 31.4 hours and 26 cycles since that check.

The airplane was equipped with two PWC JT15D-5 dual-spool turbofan engines with a takeoff thrust rating of 2,965 pounds. The No. 1 (left) engine was SN PCE-JA0521 and had operated 662.3 hours and 604 cycles since new and the No. 2 engine was SN PCE-JA0407 and had operated 4,010.3 hours and 3,359 cycles since new.

According to the Flight Options load manifest for the incident flight the gross weight of the airplane at departure was 16,061 pounds and the maximum allowable takeoff weight was 16,300 pounds. The airplane was loaded with a center of gravity (CG) of 28.1% mean aerodynamic chord (MAC), with an acceptable CG range of 17.2 - 31.7 MAC.

There were no open maintenance items in the airplane's logbook.

METEOROLOGICAL INFORMATION

There were widespread thunderstorms with cirrostratus outflow over the southeastern US at the incident time. Weather data obtained by a Safety Board meteorologist indicated the airplane overflew an area of convective activity, with tops above FL420 to the southwest of the route. The pilots reported that while cruising at FL400 they were clear of all clouds, and during an intermediate cruise at FL380 for about 15 minutes prior to the loss of power, they were about 400 to 500 feet above the cloud tops with good visibility and no turbulence. The captain reported that at the time of the flameout, they were in the clear, but within about five miles of a convective cloud buildup.

COMMUNICATIONS

No communications problems with ATC were noted at any time during the accident sequence. The crew promptly and effectively advised ATC of the situation, and ATC provided vectors and additional information to assist in the forced landing. Inter-crew communication was hampered by a partially extracted microphone plug on one of the oxygen masks. See Survival Aspects section.

AIRPORT INFORMATION

Jacksonville International Airport is located approximately 9 miles north of the city of Jacksonville, Florida. It serves mostly air carrier and commuter aircraft, and has a control tower and radar approach control. Runway 7/25 is 10,000 feet long and 150 feet wide at an elevation of 29 feet above sea level. It is served by a full instrument landing system (ILS) approach, has a 4-light precision approach path indicator (PAPI), and an 2,400 foot high intensity approach lighting system with centerline sequenced flashers able to support category II or III instrument approach minimums.

FLIGHT RECORDERS

The Cockpit Voice Recorder, an L3 Communications, model A100S, part number S100-0080-00, serial number 000117255, was removed from the airplane and sent to the NTSB recorder laboratory. Audio quality was good. The airplane was not equipped with a Flight Data Recorder, nor was it required to be.

SURVIVAL ASPECTS

The pilot-in-command, who was seated in the right cockpit seat, reported the oxygen mask would not stay in place after he had donned it. He reported that he had no facial hair at the time of the incident. He said that after pressing buttons to expand the harness, he removed his headset and glasses and placed the mask over his head. Upon releasing the buttons, the mask would slide vertically up his face and he had to repeatedly pull the mask down in order to use the microphone. The mask, manufactured by B/E Aerospace, Inc., Lenexa, Kansas, part number 174262-12 Rev C, SN 11185, was removed from the airplane for further examination. Examination by the manufacturer revealed that the hose swivel and microphone wire were not correctly assembled to the regulator such that the microphone wire limited the hose swivel to approximately 360 degrees before the wire impeded the swivel's rotation. Functional tests of the mask were nominal, and the manufacturer concluded that the misassembly of the hose swivel and microphone wire could have limited the effective length of the hose and might have caused pulling on the mask during use. The mask was reassembled properly and returned to Flight Options.

TESTS AND RESEARCH

Fuel was collected from the left and right engines' fuel filter bowls, wing tank sumps and the fuselage tank sumps. The samples were tested for flash point, density/specific gravity, freezing point, and the presence of the fuel system icing inhibitor (FSII). The testing revealed the fuel conformed to the specifications for Jet A. The testing also revealed that the amount of the FSII in the fuel was marginally less than the recommended concentration.

A functional test of the engines per the PWC maintenance manual was performed at Jacksonville. All parameters were within specified criteria.

The airplane underwent a flight evaluation to determine if the right engine would "core lock" after a rapid shutdown at high altitude from cruise power. Core lock occurs when the high and/or low pressure rotors mechanically lock with the static structure during a rapid shut down from high power and prevent the rotors from rotating, which then prevents the engine from being started. The airplane's right engine was shutdown three times using parameters similar to the event and was able to be restarted each time using either a windmill restart or a starter-assisted restart procedure.

The right engine was disassembled for examination and did not reveal any evidence of binding that would have prevented it from restarting. Several components (the starter-generator, hydraulic pump, hydromechanical unit [HMU], fuel pump, flow divider, and bleed air actuator) were removed for testing and all were serviceable. Fuel filters were removed and examined for contamination, and none was found. Testing of the filters revealed only an insignificant leak in one filter.

PWC initiated a Root Cause Analysis if this event and other flameout events. The study identified two possible contributors to the Beechjet 400A dual-engine flameouts: ice accumulation in the engine compressor and ice formation in the P3 signal pressure line to the HMU.

PWC's study determined that the ice crystals could partially melt passing through the low-pressure compressor due to the increase in temperature of the air being compressed. The study also determined that with the engine anti-ice turned off, it was theoretically possible for ice crystals to build up on the leading edges of the front inner compressor stator leading edges. Any change in engine speed would change the angle of incidence of the airflow into the compressor stators. If a significant build up of ice had occurred, a change in the airflow's angle of incidence could cause any ice that had accreted on the leading edges of the stators to break away and would result in an engine surging or possibly flaming out.

PWC also developed a rig test to demonstrate the effect of a P3 line blockage on the HMU response. (Flight tests indicated that the temperature of the P3 line went below freezing at the event conditions.) The results of those tests showed that if the P3 line was blocked when the power lever was retarded, the Electronic Engine Control (EEC) would decrease the fuel flow while the HMU P3 bellows maintained its pressure. If the P3 line became unblocked due to either the pressure differential or the warm fuel melting the ice blockage, the sudden drop in the HMU P3 bellows pressure would result in the fuel flow dropping faster than in a normal rapid engine deceleration.

A 1998 study published in the "Journal of Aircraft" (Vol. 35 #1), a 2006 paper published by American Institute of Aeronautics and Astronautics, and information from the Federal Aviation Administration's (FAA) engine icing specialist, agree that convective weather storms can lift significant amounts of moisture into the upper atmosphere and the blowoff from the tops of these convective storms can contain significant amounts of ice crystals, which can adversely affect turbine engine operation.

ORGANIZATIONAL AND MANAGEMENT INFORMATION

Flight Options was founded in October 1998 as a fractional jet management company. Flight Options was approved for 14 CFR Part 135 on-demand operations in 1979 when it was operating as Miller Aviation. In December 2001, Flight Options combined operations with Raytheon Travel Air, effectively doubling the size of the company and moving the company into the sale of both new and pre-owned aircraft. In December 2005, Flight Options became a wholly-owned subsidiary of Raytheon. At the time of the accident, the Flight Options' fleet consisted of 85 Raytheon Beechjet 400A airplanes and 95 other business jet type aircraft. Flight Options employed 850 pilots among a total workforce of 1300. Flight Options is headquartered in Cleveland Ohio, and operates a 24-hour dispatch and operation facility at the Cuyahoga County Airport.

ADDITIONAL INFORMATION

On April 23, 2000, a Beechjet 400A experienced a dual-engine flameout event near Macapa, Brazil. The event was reported to Raytheon but was not investigated by the Brazilian authority. However, typical weather conditions in the area are tropical with convective activity quite common. On November 6, 2006, another Beechjet 400A experienced a single engine flameout event near convective weather in the vicinity of Rio de Janeiro, Brazil.

On July 12, 2004, a Beechjet 400A airplane experienced a dual-engine flameout near Sarasota, Florida over the Gulf of Mexico. The pilots were able to get one engine restarted and the airplane diverted to Sarasota for a successful landing. (NTSB investigation ENG04IA021). The pilots stated that they were in instrument meteorological conditions and they had just retarded the power levers to comply with an ATC clearance to descend when both of their engines flamed out. Satellite imagery showed that there were several convective weather cells in the area where the engines flamed out.

On June 14, 2006, a Beechjet 400A experienced a dual engine flameout event near Norfolk, Virginia. (NTSB investigation ENG06IA020) This airplane was enroute from Quonset Point, Rhode Island, to Charleston, South Carolina, at FL380 in the vicinity of convective weather associated with a tropical storm. Upon reducing power for descent, the eng

NTSB Probable Cause

The dual-engine flameout due to high-altitude ice crystals that had accreted onto the JT15D-5 engines' compressor vanes and were ingested into the engine when the pilots retarded the power levers, resulting in compressor surges and rapid reduction in fuel flow due to temporary ice blockage of the combustion pressure return line, and additionally preventing an in-flight restart. Contributing to the cause of the dual-engine flameout was the lack of training on the hazards of high-altitude ice crystals to gas turbine engines and guidance to the pilots to activate the engine anti-ice system in conditions where high-altitude ice crystals may exist.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.