Flight Design CTLS accident near Boulder City, Nevada, May 7, 2019
On May 7, 2019 at about 11:00 pm local time, a 2013 Flight Design CTLS, registered N423EB, was substantially damaged in an accident during approach (VFR go-around) near Boulder City, Nevada (Boulder City Muni airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s improper monitoring and failure to maintain airspeed during a critical phase of flight, which resulted in an exceedance of the airplane’s critical angle of attack, an aerodynamic stall, and subsequent impact with terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 7, 2019 · about 11:00 pm local time
- Place
- Boulder City, Nevada · Boulder City Muni · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Flight Design CTLS Undesignat, built 2013
- Registration
- N423EB · no longer on the register · serial F-12-07-05
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot departed on a local flight with a passenger to a nearby lake. As the airplane reached the lake, the pilot perceived a sudden increase in his indicated airspeed. He responded by retarding the throttle to the idle position then advancing the throttle back to full power, at which point he observed a warning light for an engine control unit “Lane B” failure and a message on the primary flight display (PFD), “Rotax: Land Aircraft.” The pilot immediately returned to the airport and performed a rapid descent when he realized that he was high for the approach. He was unsuccessful in reducing his airspeed while over the first half of the runway and decided to execute a go-around maneuver as the airplane passed midfield. An eyewitness reported that when he observed the airplane attempt the go-around at the end of the runway, the engine did not “initially” sound like it reached full power. The airplane subsequently stalled and impacted terrain. According to the engine manufacturer, the “Lane B” failure would not have affected engine performance, and recorded engine and aircraft parameters indicated the engine continued to run and respond to throttle position changes normally throughout the flight. The data showed the unexplained increase in airspeed occurred following a change in the throttle position and the resultant increase in engine rpm. The recorded data are consistent with the pilot’s account of events leading up to the point the go-around was initiated. The data indicated that the throttle was moved to 95% about 20 seconds before the airplane stalled. The engine rpm increased, but the airspeed decreased from 52 knots to 35 knots and the angle of attack increased to 99% during that time. A postaccident examination of the airplane revealed no preimpact mechanical failures or anomalies that could have precluded normal flight. The accident is consistent with the pilot failing to monitor the airplane’s performance during the return to the airport, which resulted in the need to go around due to being too fast to land on the remaining runway. During the go-around maneuver, the pilot did not advance the throttle to 100%, which resulted in the airspeed decreasing and angle of attack increasing until the airplane stalled.
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
- Sys/Comp malf/fail (non-power) during enroute
- Aerodynamic stall/spin during approach (VFR go-around) defining event
- Collision with terrain or object (not controlled flight into terrain) during approach (VFR go-around)
The NTSB's findings
- cause Personnel issues › Psychological › Attention/monitoring › Attention › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 480 hours in all; 232 in this make and model; 15 in the last 90 days; 4 in the last 30 days; 480 as pilot in command
- Last flight review: January 4, 2019
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 511.9 hours
- Last inspection: annual inspection, December 24, 2018; 41 hours since
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912 iS2 (piston); 512 hours total
The flight
- Departed from: BVU Boulder City NV at 10:37 pm
- Destination: BVU Boulder City NV
- Flight plan: none
- Runway 15, 3,852 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 250° at 13 knots
- Visibility: 10 statute miles
- Sky: scat at 10,000 ft
- Temperature: 84°F (29°C), dew point 32°F (0°C)
- Altimeter: 29.78 inHg
- Observation at 9:15 pm from KBVU, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
16 documents, released by the NTSB on May 4, 2022. 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.
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.
