Aviation Crash Map

Embraer EMB 505 N322QS

19 September 2014 · Conroe, Texas, United States · No injuries

Summary

On 19 September 2014 at about 13:47 local time, a Embraer EMB 505 registered N322QS, operated by NetJets Aviation, Inc., was involved in an accident near Conroe, Texas, United States. 2 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 13:47
Classification
Accident
Location
Conroe, Texas, United States
Nearest airport
Lone Star Executive Airport (CXO)
Coordinates
30.3600, -95.4144
Aircraft
Embraer EMB 505
Registration
N322QS
Category
Airplane
Year built
2013
Engines
2
Operating rule
Part 91: General Aviation
Purpose of flight
Positioning
Phase of flight
Not recorded
Route
Nashville → Conroe
Aircraft damage
Substantial
Weather
IMC
Light
Day
NTSB number
CEN14FA505

People

Nobody was injured.

On board Died Serious Minor Uninjured
2 0 0 0 2

Probable cause

The second-in-command's (SIC) engagement of the emergency parking brake (EPB), which decreased the airplane's braking performance and prevented it from stopping on the available runway. Contributing to the SIC's decision to engage the EPB was the lower-than-anticipated deceleration due to a wet-runway friction level that was far lower than the levels used to determine the wet-runway stopping distances in the Airplane Flight Manual (AFM) and necessitated a landing distance considerably greater than that published in the AFM.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The pilot-in-command (PIC) and second-in-command (SIC) were conducting a positioning flight. According to the dispatch flight release, the pilots planned to land on runway 14, which was assumed to be wet. Before the flight, notices to airmen (NOTAMs) had been issued, which stated that the runway 14 threshold had been displaced 3,377 ft and that the instrument landing system and RNAV instrument approaches were not available. Although the NOTAMs were included in the flight release paperwork, dispatch personnel overlooked them, which resulted in flight planning numbers predicated on the full length of runway 14. During the approach, the pilots listened to the automatic terminal information service information and then became aware that runway 14 was shortened due to construction. Subsequently, the pilots calculated the landing distance required to land on a wet runway and chose to land on runway 1, which was the longer runway. The PIC reported that, during the approach, they encountered light rain but that the rain was moving away from the airport, which alleviated any concern regarding standing water on the runway. A review of flight data recorder data showed that the SIC flew a stabilized approach 9 knots above the reference speed (Vref) and that the airplane touched down 903 ft from the runway threshold at a groundspeed of 118 knots. The SIC stated that he began braking with half pressure and continued to increase the brake pressure to maximum, which was the normal braking procedure, but that the airplane did not appear to be decelerating. FDR data confirmed that the SIC began applying the brakes immediately upon touchdown and progressively commanded full braking performance from the brake system. The PIC informed the SIC that they needed to slow down, and the SIC replied that he had "no braking." The SIC then applied the emergency parking brake (EPB), but the airplane still did not slow down. FDR data indicated that the airplane achieved its maximum deceleration during the landing roll before the application of the EPB. FDR data showed that, once the SIC applied the EPB, the wheel speed dropped to 0. After determining that there was insufficient runway remaining for a go-around, the pilots realized that the airplane was going to exit the end of the runway. Subsequently, the airplane began to skid along the runway, which resulted in reverted-rubber hydroplaning, thus decreasing the stopping performance, and then exited the departure end of the runway and continued about 400 ft in soft terrain before it impacted a ditch and came to a stop. An examination of the brake system and data downloaded from the brake control unit indicated that the brake system functioned as commanded during the landing. Analysis of the runway surface and the amount of precipitation showed that there should have been no standing water on the runway. Landing distance calculations performed in accordance with the aircraft flight manual (AFM) showed that, even though the SIC exceeded Vref, the airplane should have been able to stop on the available runway. According to the National Transportation Safety Board's airplane performance study, the maximum wheel braking friction coefficient achieved during the portion of the ground roll before the application of the EPB was significantly less than the maximum wheel braking coefficient that would have been expected given the unfactored wet-runway landing distances published in the AFM. However, the study determined that, if the EPB had not been engaged and airplane had maintained the braking friction level attained during the landing roll before the engagement of the EPB, it would have been able to stop on the available runway. Therefore, the SIC's application of the EPB, which locked the wheels, reduced the friction level, and decreased the braking performance, prevented the airplane from stopping on the available runway. Nonetheless, the braking friction deficit observed in this accident showed that the stopping performance of the airplane was more consistent with AFM landing distances for runways contaminated with standing water than for runways that were merely "wet" even though it was determined that the runway could not have been flooded. Since the accident, the operator has issued a flight operations bulletin instructing pilots to conduct a landing distance assessment using the AFM contaminated runway performance data for the lowest contamination depth when the following three conditions exist: 1) the runway did not have a treated surface, 2) thrust reversers were deferred or not installed, and 3) the airport was reporting rain or heavy rain.

Quoted verbatim from the NTSB record.

Other Embraer EMB-505 accidents

Date Aircraft Location Operator Outcome Died
23 Nov 2014 Embraer EMB-505
C-GJOL
Palm Springs, California, United States - No injuries -
26 Jul 2016 Embraer EMB-505
N362FX
Sugar Land, Texas, United States Flight Options LLC Minor injuries -
26 Aug 2021 Embraer EMB-505
N413N
Banner Elk, North Carolina, United States Nicholas Services LLC No injuries -

Other accidents in this area

Date Aircraft Location Operator Outcome Died
20 Jul 2014 Cessna 177B
N5511B
Georgetown, Texas, United States - No injuries -
22 Apr 2014 Crow MUSTANG II
N48MK
Morton, Texas, United States - Serious injuries -
25 Oct 2014 Stol UC 1
N950TB
Jacksonville, Texas, United States Yellow Peril Aero LLC Minor injuries -
12 Jun 2014 Air Tractor AT 301
N8593S
Pearsall, Texas, United States Smith Company Flying Service No injuries -
10 Sep 2014 Smith AEROSTAR 601P
N711YM
Austin, Texas, United States Anderson David Fatal 1
4 Jun 2014 Teunis STARDUSTER TOO SA300
N8DT
Fort Worth, Texas, United States Carter Robert E Serious injuries -

All 170,864 records in United States