The U.S. aircraft register, updated daily
Accidents · NTSB CEN14FA505 · Final report

Embraer EMB 505 accident near Conroe, Texas, September 19, 2014

On September 19, 2014 at about 1:47 pm local time, a 2013 Embraer EMB 505, registered N322QS, was substantially damaged in an accident during landing (landing roll) near Conroe, Texas (Lone Star Executive Airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 19, 2014 · about 1:47 pm local time
Place
Conroe, Texas · Lone Star Executive Airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Embraer EMB 505, built 2013 · all EMB 505s on the register
Registration
N322QS · registry record · serial 50500165
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during landing (landing roll) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
  3. Landing gear collapse during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Copilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Not specified
  • cause Organizational issues › Development › Selection/certification/testing › Equip certification/testing › Manufacturer
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Copilot
  • factor Organizational issues › Development › Selection/certification/testing › Document/info verification › Manufacturer
  • factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Not attained/maintained

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: balloon
  • Flight time: 13,466 hours in all; 322 in this make and model
  • Last flight review: May 12, 2014
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 9,861 hours in all; 361 in this make and model
  • Last flight review: May 12, 2014
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 597.7 hours
  • Last inspection: approved inspection programme, July 17, 2014
  • Maximum gross weight: 18,387 lb
  • Seats: 9
  • Landing gear: retractable
  • Engine 1: P&W Canada PW535E (turbofan); 834 hours total
  • Engine 2: P&W Canada PW535E (turbofan); 834 hours total
  • Operator: Netjets Aviation, Inc.

The flight

  • Departed from: BNA Nashville TN at 12:06 pm
  • Destination: CXO Conroe TX
  • Flight plan: IFR
  • Runway 01, 5,000 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 2 statute miles
  • Sky: broken clouds at 8,000 ft; a few clouds at 500 ft
  • Temperature: 73°F (23°C), dew point 72°F (22°C)
  • Altimeter: 29.93 inHg
  • Observation at 1:41 pm from CXO

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

32 documents, released by the NTSB on April 13, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
2 Crew Statements PDF, 2 pages View Download
3 Aircraft Performance PDF, 187 pages View Download
4 Aircraft Performance Study Errata #1 PDF, 1 page View Download
5 Cxo Runway 1 Examination Test Plan PDF, 37 pages View Download
6 Kcxo Runway 1 Examination Test Report PDF, 42 pages View Download
7 Flight Data Recorder PDF, 12 pages View Download
8 Cockpit Voice Recorder Group Chairman's Factual Report PDF, 25 pages View Download
9 Meggitt Bcu Report PDF, 22 pages View Download
10 Weather Information PDF, 4 pages View Download
11 Record of Conversations (2) PDF, 2 pages View Download
12 Netjets Flight Release PDF, 20 pages View Download
13 Weight and Balance PDF, 3 pages View Download
14 Performance Data PDF, 1 page View Download
15 Investigating Runway Overruns Presentation PDF, 22 pages View Download
16 Aircraft Maintenance Manual Excerpts PDF, 76 pages View Download
17 FAA Ac 91-79A PDF, 39 pages View Download
18 FAA Ac 25-23 PDF, 24 pages View Download
19 FAA Ac 23-8C PDF, 12 pages View Download
20 FAA Safo 15009 PDF, 2 pages View Download
21 FAA Safo 06012 PDF, 11 pages View Download
22 Phenom Flight Operations Letter PDF, 9 pages View Download
23 Emb 505 Type Certificate Exemption PDF, 7 pages View Download
24 Embraer Deceleration Chart PDF, 1 page View Download
25 Embraer AFM Landing Technique PDF, 1 page View Download
26 Roswell Runway Pavement Macrotexture Retest PDF, 47 pages View Download
27 NTSB Recommendation A-07-57 PDF, 6 pages View Download
28 NTSB Recommendation A-07-58 Through -64 PDF, 14 pages View Download
29 Photo Array PDF, 6 pages View Download
30 Statement of Party Representatives to NTSB Investigation PDF, 4 pages View Download
31 Netjets Party Submission PDF, 10 pages View Download
32 Njasap Party Submission PDF, 11 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.