FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23FA301 · Glasair Glastar

4 Aug 2023 · Idaho City, ID, United States

Glasair Glastar · Accident: loss of control on ground during takeoff

From Caldwell Executive Airport (EUL) to an unrecorded destination

Report a problem

Event

NTSB case
WPR23FA301
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Glasair Glastar

Aircraft type
Glasair GLASTAR
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N617G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Caldwell Executive Airport (EUL), Caldwell, IDTo not recorded
Aircraft age
About 17 years (built 2006)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot and a friend were preparing to depart the airfield in their respective airplanes when the accident pilot began to feel physical discomfort. He entered nearby woods to relieve himself and was gone for about 10 minutes. His decision not to walk a short distance to the airport restroom suggests that his discomfort required immediate attention. Upon his return, he resumed preparing to depart. The friend and the accident pilot then taxied their airplanes to the gravel runway. The friend was first to depart and made multiple attempts to communicate over the radio with the accident pilot but received no reply. An earwitness heard the airplane’s engine power up, and the sound continued until “it just stopped.” He then heard a “slap.” It is likely that the accident pilot applied takeoff power to depart, based upon the loud engine noise heard by the witness and the postaccident positions of the throttle and propeller levers. The airplane remained mostly on the ground and on a left-arcing path until it impacted trees beside the runway. One tree exhibited a deep gouge consistent with impact from a propeller blade that was under power. Evidence was consistent with the airplane continuing to accelerate until it impacted the trees. No skid marks associated with the application of wheel brakes were identified. Examination of the airplane revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation. Engine data revealed normal operation before the application of takeoff power. The friend reported that he had no problems controlling the airplane and that the airplane sounded normal upon arrival to the airfield. Toxicology results indicate that the pilot had used cetirizine. It is possible he may have been experiencing some associated impairing effects, such as mild sedation, at the time of the accident. However, the cetirizine levels in cavity blood and urine cannot reliably be used to predict impairment. An autopsy of the pilot and a medical review revealed no evidence of a preaccident medical event. The pilot’s physical discomfort that required urgent action before the flight suggests that he experienced some type of physical ailment during the preflight inspection. It is possible that after the application of takeoff power to depart, the pilot experienced a physical or medical event that precluded him from operating the airplane; however, no evidence of any such ailment was discovered. The apparent lack of throttle reduction, lack of braking skid marks in the gravel, and the left yawing indications, which were likely the result of engine torque and propeller asymmetrical forces (P-factor), suggest that after applying takeoff power, the pilot did not or could not control the airplane for reasons that could not be determined and he did not attempt to abort the takeoff.

Probable cause

The pilot’s loss of airplane control during takeoff for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23FA301
Event ID
20230804192795
Case number
WPR23FA301
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 1d9d8ca226d283ff5103ddaf83c4d8646105b036c65134b0f98cec971c9cfce2; retrieved 2026-09-15T08:04:15.322Z.