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

Embraer S.A. EMB-500 accident near Sugarland, Texas, November 21, 2014

On November 21, 2014 at about 4:10 pm local time, a 2010 Embraer S.A. EMB-500, registered N584JS, was substantially damaged in an accident during landing near Sugarland, Texas (Sugarland Regional 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 visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's engagement of the emergency parking brake during the landing roll, which decreased the airplane's braking performance and prevented it from stopping on the available runway. Contributing to the pilot's decision to engage the emergency parking brake was the expectation of a faster rate of deceleration and considerably shorter wet runway landing distance provided by the airplane flight manual than that experienced by the crew upon touchdown and an actual wet runway friction level lower than the assumed runway fiction level used in the calculation of the stopping distances published in the airplane flight manual.

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

What the record shows

Date
November 21, 2014 · about 4:10 pm local time · cases in 2014
Place
Sugarland, Texas · Sugarland Regional Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Embraer S.A. EMB-500, built 2010
Registration
N584JS · registry record · serial 50000140
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

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

The pilots of the very light jet were conducting a positioning flight in instrument meteorological conditions. The flight was cleared by air traffic control for the instrument landing system (ILS) approach; upon being cleared for landing, the tower controller reported to the crew that there was no standing water on the runway. Review of the airplane's flight data recorder (FDR) data revealed that the airplane reached 50 ft above touchdown zone elevation (TDZE) at an indicated airspeed of 118 knots (KIAS). The airplane crossed the runway displaced threshold about 112 KIAS, and it touched down on the runway at 104 KIAS with about a 7-knot tailwind. FDR data revealed that, about 1.6 seconds after touchdown of the main landing gear, the nose landing gear touched down and the pilot's brake pedal input increased, with intermediate oscillations, over a period of 7.5 seconds before reaching full pedal deflection. During this time, the airplane achieved its maximum wheel braking friction coefficient and deceleration. The cockpit voice recorder recorded both pilots express concern the that the airplane was not slowing. About 4 seconds after the airplane reached maximum deceleration, the pilot applied the emergency parking brake (EPB). Upon application of the EPB, the wheel speed dropped to zero and the airplane began to skid, which resulted in reverted-rubber hydroplaning, further decreasing the airplane's stopping performance. The airplane continued past the end of the runway, crossed a service road, and came to rest in a drainage ditch. Postaccident examination of the brake system and data downloaded from the brake control unit indicated that it functioned as commanded during the landing. The airplane was not equipped with thrust reversers or spoilers to aid in deceleration. The operator's standard operating procedures required pilots to conduct a go-around if the airspeed at 50 ft above TDZE exceeded 111 kts. Further, the landing distances published in the airplane flight manual (AFM) are based on the airplane slowing to its reference speed (Vref) of 101 KIAS at 50 ft over the runway threshold. The airplane's speed at that time exceeded Vref, which resulted in an increased runway distance required to stop; however, landing distance calculations performed in accordance with the AFM showed that the airplane should still have been able to stop on the available runway. An airplane performance study also showed that the airplane had adequate distance available on which to stop had the pilot continued to apply maximum braking rather than engage the EPB. The application of the EPB resulted in skidding, which increased the stopping distance. Although the runway was not contaminated with standing water at the time of the accident, the performance study revealed that the maximum wheel braking friction coefficient was significantly less than the values derived from the unfactored wet runway landing distances published in the AFM, and was more consistent with the AFM-provided landing distances for runways contaminated with standing water. Federal Aviation Administration Safety Alert for Operators (SAFO) 15009 warns operators that, "the advisory data for wet runway landings may not provide a safe stopping margin under all conditions" and advised them to assume "a braking action of medium or fair when computing time-of-arrival landing performance or [increase] the factor applied to the wet runway time-of-arrival landing performance data." It is likely that, based on the landing data in the AFM, the crew expected a faster rate of deceleration upon application of maximum braking; when that rate of deceleration was not achieved, the pilot chose to engage the EPB, which only further degraded the airplane's braking performance.

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. Other weather encounter during landing
  2. Landing area overshoot during landing
  3. Collision during takeoff/land during landing defining event
  4. Runway excursion during landing

The NTSB's findings

  • cause Personnel issues › Action/decision › (general) › (general) › Pilot
  • cause Organizational issues › Development › Selection/certification/testing › Document/info verification › FAA/Regulator

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 6,311 hours in all; 410 in this make and model; 77 in the last 90 days; 20 in the last 30 days
  • Last flight review: July 7, 2014
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 4,232 hours in all; 814 in this make and model; 103 in the last 90 days; 45 in the last 30 days; 2,602 as pilot in command
  • Last flight review: September 12, 2014
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,854 hours
  • Last inspection: type not recorded, October 31, 2014
  • Maximum gross weight: 10,472 lb
  • Landing gear: fixed
  • Engine 1: P&W Canada PW617F-E (turbofan); 0 hours total
  • Engine 2: P&W Canada PW617F-E (turbofan); 0 hours total
  • Operator: Superior Air Charter, LLC

The flight

  • Departed from: HOU Houston TX
  • Destination: KSGR Sugarland TX
  • Flight plan: IFR
  • Runway 35, 8,000 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 130° at 8 knots
  • Visibility: 6 statute miles
  • Sky: broken clouds at 3,300 ft; a few clouds at 800 ft
  • Temperature: 66°F (19°C), dew point 64°F (18°C)
  • Altimeter: 30.14 inHg

Injuries

FatalSeriousMinorNone
Flight crew2

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

14 documents, released by the NTSB on September 15, 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.

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

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN15LA057.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.