CEN26FA275 · Beech E18S
Skydog Air Beech E18S · Accident: loss of control in flight during initial climb
Event
- NTSB case
- CEN26FA275
- 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
- Ongoing
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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
Beech E18S
- Aircraft type
- Beechcraft 18
- 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
- N210Q
- Operator
- Skydog Air
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 69 years (built 1957)
- 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
- Initial climb
- 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 in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On August 2, 2026, about 1608 central daylight time (CDT), a Beech E18S airplane, N210Q, was destroyed when it was involved in an accident near Guymon, Oklahoma. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight. The airplane was purchased by the pilot on June 22, 2026. According to the seller, the pilot was re-positioning the airplane to South Carolina. The seller stated that he had flown about 6 hours with the pilot in the accident airplane over two flights from June 21 to June 27. The pilot arrived on August 1 to pick up the airplane. The flight took place over multiple time zones, all times referenced will be in CDT. On August 1, the airplane departed Lebanon State Airport (S30), Lebanon, Oregon, about 2108 and arrived at Winnemucca Municipal Airport (WMC), Winnemucca, Nevada, at 0015. The airplane was refueled with 175 gallons of 100 low-lead aviation fuel before departing about 0111, August 2. On August 2, about 0440, the airplane landed at Four Corners Regional Airport (FMN), Farmington, New Mexico. The airplane was refueled with 88 gallons of 100 low-lead aviation. The airplane departed FMN about 1258 for Guymon Municipal Airport (GUY), Guymon, Oklahoma. The airplane landed at GUY about 1509. According to the GUY airport manager, the pilot refueled the airplane with 211.7 gallons of fuel and added oil to both engines. He spoke briefly with the pilot and discussed a fuel stop near Little Rock, Arkansas. At 1606, the pilot announced his departure from runway 18 at GUY on the common traffic advisory frequency (CTAF). According to witnesses, after departing runway 18, the airplane was observed making a left bank and the pilot announced on CTAF that he was departing to the east. Witnesses observed the airplane make a turn to the east and continue the turn to the north while descending in a nose low, left-wing-low attitude. Multiple security videos captured the accident sequence. The footage was sent to the NTSB Vehicle Performance Division for further analysis. The airplane impacted a grass covered field in a wings-level, flat pitch attitude on a heading of about 015°. The aircraft came to rest upright about 80 ft north of the initial impact point. A post-impact fire consumed the majority of the fuselage and melted the wings and tail as seen in figure 1. All major components of the airplane were identified. Both engines were separated from the airframe and located near the main wreckage. Both propeller hubs remained attached to the engines. The propeller blades showed varying degrees of bending, twisting, chordwise scratching and polishing. Examination of the flight controls found no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.
Figure 1. Main wreckage The pilot held a commercial certificate with ratings for airplane single-engine land, airplane single-engine sea, airplane multi-engine land, airplane multi-engine sea, instrument airplane and a BE-1900 type rating. Additionally, he held an Airline Transport Pilot certificate for rotorcraft-helicopter. He reported a total flight experience of 12,000 hours on an application for an FAA first-class medical certificate, dated December 24, 2025. The airplane was recovered to a secure facility for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN26FA275
- Event ID
- 20260802203501
- Case number
- CEN26FA275
- 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. 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: c82dbb5195189d90791db354dee4a05b3fed308b3c3f3c2b88d01191852842f8; retrieved 2026-09-15T09:19:09.431Z.