Monday, March 14, 2016

Raytheon 400A Beechjet, Flight Options LLC, N465FL: Accident occurred March 14, 2016 at Richard B. Russell Regional Airport (KRMG), Rome, Floyd County, Georgia (and) Embraer EMB-505 Phenom 300, Flight Options LLC, N327FL, Accident occurred August 05, 2013 at Flying Cloud Airport (KFCM), Eden Prairie, Hennepin County, Minnesota

The National Transportation Safety Board did not travel to the scene of this accident. 

Aviation Accident Preliminary Report - National Transportation Safety Board: http://app.ntsb.gov/pdf 

FLIGHT OPTIONS LLC:   http://registry.faa.gov/N465FL

FAA Flight Standards District Office: FAA Atlanta FSDO-11

NTSB Identification: ERA16LA131
14 CFR Part 91: General Aviation
Accident occurred Monday, March 14, 2016 in Rome, GA
Aircraft: RAYTHEON AIRCRAFT COMPANY 400A, registration: N465FL
Injuries: 1 Minor, 1 Uninjured.

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

On March 14, 2016, at 1508 eastern daylight time, a Raytheon Aircraft Company 400A, N465FL, was substantially damaged during a runway excursion while landing at Richard B. Russell Regional Airport (RMG), Rome, Georgia. The pilot was uninjured and the co-pilot received minor injuries. The airplane was registered to Flight Options, LLC and was being operated in accordance with Title 14 Code of Federal Regulations Part 91 as a positioning flight that originated at Jackson County Airport-Reynolds Field (JXN), Jackson, Michigan. The flight was operating under an instrument flight plan and visual meteorological conditions were reported at the airport at the time of the accident.

According to the crew, they began their descent while under Atlanta Air Route Traffic Control and retrieved the weather conditions from the automated surface observing system at RMG, which indicated the winds were variable at 6 knots. They requested and were cleared for the visual approach to runway 7, which was 4,495 feet-long.

While in the traffic pattern and abeam the runway numbers, the crew lowered the landing gear and deployed 20 degrees of flaps, followed by 30 degrees on the base leg. On final approach, the crew stated that the turbulence was moderate and the airspeed started fluctuate and decrease to Vref. They responded by adjusting engine power on short final, and noted that "considerable power" was necessary to maintain airspeed. The airplane touched down at the Vref speed of 112 kts inside the touchdown zone, but the ground speed appeared to be fast.

The crew activated the speed brakes, and the pilot applied the wheel brakes (the airplane was not equipped with thrust reversers). The crew then increased their braking to maximum, and when it was evident that the airplane not going to stop before the end of the runway, they activated the emergency brake. The airplane departed the end of the runway and travelled into the safety area, where it sank into the grass and mud as it continued forward in a slight left turn. The nose landing gear collapsed and the forward fuselage struck the ground resulting in substantial damage to the airframe. The airplane came to rest approximately 350 feet from the departure end of the runway.


The airplane was recovered from the site and retained for additional investigation.


National Transportation Safety Board - Aviation Accident Final Report: http://app.ntsb.gov/pdf

National Transportation Safety Board  - Docket And Docket Items:  
http://dms.ntsb.gov/pubdms

National Transportation Safety Board  -  Aviation Accident Data Summary:   http://app.ntsb.gov/pdf

NTSB Identification: CEN13LA462
14 CFR Part 91: General Aviation
Accident occurred Monday, August 05, 2013 in Eden Prairie, MN
Probable Cause Approval Date: 09/12/2016
Aircraft: EMBRAER S A EMB-505, registration: N327FL
Injuries: 2 Uninjured.

NTSB investigators may have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

The flight crew of the light jet was conducting a landing to a wet 5,000-ft-long runway. Their preflight calculations indicated an approach speed of 110 knots given the airplane's estimated landing weight. Data obtained from the flight recorder showed that, as the airplane descended through about 500 ft above ground level on final approach, its speed was 186 knots and its rate of descent was over 3,000 ft per minute. The airplane crossed the runway threshold about 158 knots, and touched down about 1,000 feet down the runway about 145 knots. The airplane subsequently departed the end of the runway, impacted obstructions, and came to rest upright on a four-lane highway about 1,000 ft beyond the runway surface. A postaccident examination of the engines, airframe, and braking system revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

The operator’s procedures stated that all approaches to land must be stabilized at 500 feet above airport elevation, and any approach that became unstabilized required an immediate go-around. Among the company's criteria for determining a stable approach was: airspeed no more than 20 knots over target, and descent rate no greater than 1,000 ft per minute. During the approach, the airspeed was 76 knots over the target approach speed and the descent rate of 3,000 ft per minute greatly exceeded the criteria for a stabilized approach.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The flight crew's failure to execute a go-around during a non-stabilized approach, which resulted in a runway overrun.

On August 5, 2013, at 0848 central daylight time, N327FL, an Embraer S.A. EMB-505, multi-engine turbofan airplane, was substantially damaged during landing at Flying Cloud Airport (FCM), Eden Prairie, Minnesota. The two pilots were not injured. The airplane was registered to and operated by Flight Options, LLC; Cleveland, Ohio. Day visual meteorological conditions (VMC) prevailed at the time of the accident and an instrument flight rules flight plan had been filed for the 14 Code of Federal Regulations Part 91 positioning flight. The airplane had departed Pittsburgh International Airport (PIT), Pittsburgh, Pennsylvania, at 0731 eastern daylight time and was destined for FCM.

Both pilots reported that the airplane had been on a fast and steep visual approach when it then landed on runway 10R at FCM. They also reported that the indicated airspeed was about 150 to 160 knots when the airplane touched down on the runway at some point after the 1,000 foot marker. The airplane departed the end of the 5,000 foot long runway and impacted an airport boundary fence and other obstructions before coming to rest upright on a four-lane highway about 1,000 feet from the runway surface. The impact resulted in substantial damage to both wings and the fuselage.

A hand written takeoff and landing data card prepared by the flight crew before their arrival at FCM showed their expected landing weight was 14,000 pounds, their calculated Vref speed was 106 knots, and the Vap speed was 110 knots, with the flaps set at position 3. The airport elevation was noted as 906 feet. The space on the card for runway required was blank and did not have an entry.

Data on page PD35-3 in the Quick Reference Handbook (QRH) showed landing performance for an EMB-505 airplane landing at an airport at an altitude of 1,000 feet at a landing weight of 14,000 pounds, with the flaps set at position 3. When the airplane was flown at a Vref speed of 107 knots and a Vap speed of 110 knots, the expected dry runway unfactored landing distance was 2,378 feet, the expected wet unfactored landing distance was 3,000 feet, and the expected wet factored landing distance was 4,600 feet.

A combination voice and flight data recorder (CVDR) was removed from the wreckage and examined at the NTSB Vehicle Recorder Laboratory, in Washington, D.C. The cockpit voice recorder portion of the CVDR contained 2 hours and 4 minutes of excellent quality voice recordings. A cockpit voice recorder group was convened and a partial transcript was prepared for the last 32 minutes of the flight.

Data from the flight data recorder (FDR) portion of the CVDR recording contained about 107 hours of data. The accident flight was the last flight of the FDR recording and its duration was about 2 hours and 56 minutes, which included the portion of time during the preflight checks before departure from PIT.

An examination of the FDR data showed the following:

At 0846:40 the airplane was on final approach at an altitude of 2,510 feet mean sea level (msl), at an indicated airspeed of 177 knots, and was descending at 3,986 feet per minute. The airplane was then configured with the landing gear extended, the speed brake extended, and the flaps at position 1.

At 0846:40 the recorder values for both engines were about 30 percent N1, and they remained at this level until engine shutdown after the airplane came to rest.

Between 0846:40 and 0847:17 thirteen different aural warning unit (AWU) sounds were announced including multiple calls of: "whoop whoop pull up", "high speed", and "too low. terrain".

At 0847:02 the airplane was on final approach at an indicated airspeed of 186 knots, at an altitude of 1,329 feet msl, or about 423 feet above the airport, and was descending at 3,077 feet per minute.

At 0847:14 the AWU announced "two hundred".

At 0847:16 the flap lever was selected to position 2.

At 0847:18 the AWU announced "one hundred".

At 0847:18 the indicated airspeed was 168 knots and the flap lever was selected to position 3.

At 0847:24 the airplane crossed the runway threshold at an indicated airspeed of 158 knots.

At 0847:28 the airplane touched down on the runway. Indicated airspeed near the point of touchdown was between 145 and 148 knots and groundspeed was between 150 and 153 knots.

At 0847:29 brake pressures for both left and right braking systems began increasing to an initial local maxima of around 630 psi between about five and six seconds after the maximum wheel spin value was recorded. Left and right brake pressure values varied between about 140 and 740 psi until 0847:47.

At 0847:47 there was a recorded brake pedal displacement of about 35 mm of stroke for the right brake pedal and the FDR discrete for brake fail parameter changed to true. Brake pressures then dropped to a value of about 50 psi and remained near that value for the remainder of the recording.

At 0847:50 indicated airspeed was 68 knots when the airplane exited the runway surface.

At 08:48:07 indicated airspeed and groundspeed had become approximately zero knots.

FDR data for the emergency / parking brake lever discrete showed the brake to be on at the start of the flight and was then moved to the release position for taxing during the airplane's departure from PIT. The emergency / parking brake lever remained off for the remainder of the flight and was not activated during the landing at FCM.

Instructions in the QRH for a loss of normal braking on page EAP12-5 showed that when the yellow BRK FAIL message is illuminated the emergency / parking brake lever should be gently applied.

Embraer reported that the brake-by-wire system is designed such that if a failure occurs in either pedal transducer, then the system will declare a brake failure and close the main brake system shut-off valve. The brakes could then be controlled by the emergency brake system using the emergency / park brake handle. There is no anti-skid function when using this emergency brake system.

Recorded data from the brake control unit (BCU) and the FDR indicated that the brakes initially operated normally during the landing roll with the anti-skid operating. During landing, the pedal displacement gradually increased over 17 seconds until the BRK FAIL message illuminated and failure of the normal brake system occurred. The displacement of the right pedal suggests that this failure occurred as a result of over travel of the pedal beyond the mechanical stop.

The recorded data also showed that during the accident landing the emergency / parking brake handle was not actuated and remained at the off position.

Wreckage examination:

A postaccident examination of the engines and the airframe revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

The BCU was examined at the manufacturer's facility. The BCU passed a full functional test and it was returned to service.

Airport Information:

The FAA Airport/ Facility Directory, North Central U. S., indicated that FCM was a towered airport with a field elevation of 906 feet mean sea level (msl). The longest runway was 10R-28L, which was an asphalt runway 5,000 feet long by 100 feet wide. Runway 10R was oriented to 098.8 degrees true and 99.9 degrees magnetic. Records show that the asphalt surface was not grooved and did not have a porous friction course overlay.

Meteorological Information:

At 0838 the recorded weather data from FCM revealed that the wind was from 150 degrees at 4 knots, 6 miles visibility in mist, few clouds at 200 feet above ground level (agl), an overcast ceiling at 7,000 feet agl, temperature 18 degrees C, dew point temperature 17 degrees C, with an altimeter setting of 29.89 inches of mercury. Remarks indicated that rain ended at 0819 with a one hour precipitation of 0.01 inches. At 0737 FCM reported that there had been a one hour total of 0.14 inches of rain. At 0653 FCM reported that the daily total rainfall had been 0.81 inches.

At 0847:43 a security camera video frame capture photo showed the aircraft parking ramp adjacent to the runway was wet and there were pools of standing water. Photos of the roadway surface taken between 0857 and 0901 showed the pavement was wet. At 1035 a photo of the runway surface showed the pavement was wet and had several areas of standing water.

Additional Information:

FAA AC 120-108 states "A stabilized approach is a key feature to a safe approach and landing (and is) characterized by maintaining a stable approach speed, descent rate, vertical flight path, and configuration to the landing touchdown point ... at a rate of descent no greater than 1,000 feet per minute (fpm)"

FAA Safety Alert for Operators - SAFO 15009 Date: 8/11/15
Subject: Turbojet Braking Performance on Wet Runways

"Several recent runway landing incidents/accidents have raised concerns with wet runway stopping performance assumptions. Analysis of the stopping data from these incidents/accidents indicates the braking coefficient of friction in each case was significantly lower than expected for a wet runway as defined by the Federal Aviation Administration (FAA) in Federal Air Regulation (FAR) 25.109 and Advisory Circular (AC) 25-7C methods. These incidents/accidents occurred on both grooved and un-grooved or non-Porous Friction Course overlay (PFC) runways. The data indicates that applying a 15 percent safety margin to wet runway time-of-arrival advisory data as, recommended by SAFO 06012, may be inadequate in certain wet runway conditions."

FAA Advisory Circular AC No: 91-79A - Date: 9/17/14
Subject: Mitigating the Risks of a Runway Overrun Upon Landing

Paragraph 6, c, (1): "A 10 percent increase in final approach speed results in a 20 percent increase in landing distance."


Paragraph 6, j.: "Landing distances in the manufacturer-supplied AFM provide performance in a flight test environment that is not necessarily representative of normal flight operations. For those operators conducting operations in accordance with specific FAA performance regulations, the operating regulations require the AFM landing distances to be factored to ensure compliance with the pre-departure landing distance regulations. These factors should account for pilot technique, wind and runway conditions, and other items stated above. Pilots and operators should also account for runway conditions at the time of arrival (TOA) to ensure the safety of the landing. Though the intended audience of SAFO 06012 is turbojet airplanes, it is highly recommended that pilots of non-turbojet airplanes also follow the recommendations in SAFO 06012."

(1) The SAFO urgently recommends that operators develop a procedure for flightcrews to assess landing performance based on conditions actually existing at the TOA, as distinct from conditions presumed at time of dispatch. Those conditions include weather, runway conditions, the airplane's landing weight, landing configuration, approach speed, and the flightcrew deploys deceleration devices in a timely manner.

(2) Once the actual landing distance is determined, an additional safety margin of at least 15 percent should be added to that distance. Except under emergency conditions, flightcrews should not attempt to land on runways that do not meet the assessment criteria and safety margins as specified in SAFO 06012.

(3) A safety margin of 15 percent should be added, and the resulting distance should be within the runway length available. The FAA considers a 15 percent margin to be the minimum acceptable safety margin.



Appendix 1; Paragraph 2: Definitions:

j. Unfactored or Certified Landing Distance. The landing distance determined during certification as required by 14 CFR part 23, § 23.75 and 14 CFR part 25, § 25.125. The unfactored landing distance is not adjusted for any safety margin additives. The unfactored certified landing distance may be different from the actual landing distance because not all factors affecting landing distance are required to be accounted for by certification regulations.

k. Factored Landing Distance. For applicable operations, the dispatch landing distance allows the airplane to land and stop within 60 percent of the available runway when the runway is dry. The factored landing distance is the certified landing distance multiplied by 1.67, which can then be compared directly to the available landing distance. When the runway is wet, the certified distance is multiplied by 1.97 to account for the 15 percent additional runway requirement.

FAA Safety Alert for Operators SAFO 10005 - Date: 3/1/10
Subject: Go-Around Callout and Immediate Response

"It is critical to flight safety that both the pilot flying and the pilot monitoring should be able to call for a go-around if either pilot believes an unsafe condition exists. Also, although CRM principles prescribe that some cockpit decisions can be made by crew consensus, others, including the go-around callout, require immediate action, without question, because of the immediacy of the situation."

Flight Options – Flight Operations Manual
Page 4-19 – Date June 1, 2012
Subject: Go around

"Any time a "Go Around" is called, the PF will immediately execute the briefed maneuver. Any crewmember can call a "Go Around." "

Flight Options – Flight Operations Manual
Page 4-98 – Date June 1, 2012
Subject: Stabilized Approach Criteria

"All flights must be stabilized at 500' above MDA/DH when IMC or 500' above airport elevation when in VMC conditions. A go-around must be initiated if the aircraft does not meet the stabilized approach criteria … An approach is stabilized when it meets the following criteria: 1. All briefings have been conducted
2. Aircraft is fully configured … for landing
3. IAS airspeed is no more than VREF + 20 KTS and no less than VREF
4. IVSI is no more than 1000' per minute

An approach that becomes unstabilized requires an immediate go-around".

Flight Options – Part 135 / 91K Aircrew Training Manual
Page A6-11 – Date April 15, 2013
Subject: Visual Approach and Landing

The training manual pictorial shows that on base leg for a visual approach and landing the landing gear should be down, the before landing checklist should have been completed, the flaps should be at Flaps 3, the bank should not exceed 30 degreed, and the airspeed should be 120 knots. The pictorial also shows that when the airplane is crossing the runway threshold the airspeed should be at Vref.

Flight Options – Phenom 300 Aircraft Specific Standard Operating Procedures (SOP)
Page 9 – Date July 13, 2012
Subject: Visual Traffic Patterns

The SOP shows that when the airplane is at 500 feet above the airport surface on a visual approach the pilot monitoring (PM) should call out "500 FT, Stabilized" and the pilot flying (PF) should then respond with "Stabilized". If the PM calls out "500 FT, Go Around", the PF should then respond with "Go Around"

Postaccident Changes to the BCU

On September 9, 2014, Embraer issued Service Bulletin (SB) 505-32-0015, which decreases the possibility of occurrence of the loss of main brakes if a brake pedal overtravels during an emergency situation. The overtravel monitoring remains active on the airplane in case of an actual transducer failure.

The changes implemented by the SB on BCU p/n DAP00100-09 include the following:

The "ANTISKID FAIL" message will appear on CAS when one of the pedals moves above 95.8 percent. The CAS message "ANTISKID FAIL" will be triggered on ground when the aircraft is stationary for 5 seconds, in order to indicate that the brake pedal adjustment is required before next flight – no loss of anti-skid function.

The "BRK FAIL" message will appear on CAS when one pedal achieves 100 percent and the other pedal is below 60 percent (resulting in loss of main brake).

The "BRK FAIL" message will NOT appear on CAS when one pedal is at 100 percent and the other pedal is above 60 percent (no brake loss).













NTSB Identification: CEN13LA462
14 CFR Part 91: General Aviation
Accident occurred Monday, August 05, 2013 in Eden Prairie, MN
Aircraft: EMBRAER EMB-505, registration: N327FL
Injuries: 2 Uninjured.

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

On August 5, 2013, at 0848 central daylight time, N327FL, an Embraer S.A. EMB-505, multi-engine turbofan airplane, was substantially damaged during landing at Flying Cloud Airport (FCM), Eden Prairie, Minnesota. The two pilots were not injured. The airplane was registered to and operated by Flight Options, LLC; Cleveland, Ohio. Day visual meteorological conditions (VMC) prevailed at the time of the accident and an instrument flight rules flight plan had been filed for the 14 Code of Federal Regulations Part 91 positioning flight. The airplane had departed Pittsburgh International Airport (PIT), Pittsburgh, Pennsylvania, about 0730 eastern daylight time and was destined for FCM.

The pilots reported that the airplane was on a steep visual approach when they landed long and fast. The pilot flying also reported that after touchdown he could feel the pulsing of the anti-skid brakes but was unable to stop on the runway surface. The airplane departed the end of the runway and impacted the airport boundary fence coming to rest on a four-lane highway about 1,000 feet from the runway. 

At 0838 the data from FCM revealed that the wind was from 150 degrees at 4 knots, 6 miles visibility in mist, few clouds at 200 feet above ground level (agl), an overcast ceiling at 7,000 feet agl, temperature 18 degrees C, dew point temperature 17 degrees C, with an altimeter setting of 29.89 inches of mercury. Remarks indicated that rain ended at 0819 with a one hour precipitation of 0.01 inches.

A corporate jet arriving at the Flying Cloud Airport in Eden Prairie overshot the runway Monday morning, went through a fence and came to rest on a road, authorities said.

There is no immediate word on why the twin-engine plane left the runway about 8:50 a.m. and ended up partly on Flying Cloud Drive to the southeast of the airport, said Melissa Scovronski, spokeswoman for the Metropolitan Airports Commission.

The aircraft’s owner, Flight Options of Cleveland, said there were two crew members and no one else aboard the Embraer Phenom 300, which seats seven passengers. Neither crew member was hurt, said company spokeswoman Lauren Florian.

Two pilots and a man were standing outside the damaged year-old aircraft moments after the crash.

Southbound Flying Cloud Drive is closed at Pioneer Trail “until further notice,” city officials said in a statement.

Scovronski said the airport halted arrivals and departures only momentarily, as required by federal regulations.

Authorities have yet to say where the flight originated, but the independent aviation tracking service FlightAware says the plane took off from Pittsburgh International Airport and was scheduled to arrive at 8:14 a.m.

Flight Options describes itself as the world’s second-largest private aviation fleet, with more than 100 aircraft serving roughly 1,300 owners and clients.


Story and Photo Gallery:  http://kstp.com





A plane ran off the end of the runway at the Richard B. Russell Regional Airport after 3 o’clock Monday afternoon.


The nose gear of the Beechjet was damaged but both pilots were able to get out safely.


There are no serious injuries, but EMS was dispatched to the scene for one person complaining of back pain.


There was no one else on board.


The jet was from out of town.


Fire units also responded non-emergency as a precaution.


Original article can be found here:   http://wrgarome.com 


The Federal Aviation Administration will be at Richard B. Russell Regional Airport this morning to investigate how a plane ran off the runway Monday afternoon.

Airport Manager Mike Mathews said the small jet had two pilots on board but neither was injured. The nose of the plane had minor damage.

Mathews said strong winds were a factor in the crash; the jet had a tailwind that shifted when it was trying to land.

The plane went past the runway safety area and into the grass.

“It went about 600 to 800 feet,” said Mathews.

No comments: