Remos Acft GMBH Flugzeugbau REMOS GX accident near Glendale, Arizona, July 12, 2026
On July 12, 2026 at about 5:18 pm local time, a 2009 Remos Acft GMBH Flugzeugbau REMOS GX, registered N126GX, was substantially damaged in an accident during initial climb near Glendale, Arizona (Glendale Regional Airport). It was an instructional 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).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 12, 2026 · about 5:18 pm local time
- Place
- Glendale, Arizona · Glendale Regional Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Remos Acft GMBH Flugzeugbau REMOS GX, built 2009 · all REMOS GXs on the register
- Registration
- N126GX · registry record · serial 342
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On July 12, 2026, at 1018 mountain standard time, a Remos GX airplane, N126GX, was substantially damaged when it was involved in an accident near Glendale, Arizona. The flight instructor and student pilot were uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the flight instructor, the student pilot was practicing landings at Glendale Regional Airport (GEU), Glendale, Arizona. The student performed a go around and, during the initial climb, he stated that the airplane’s pitch control was “delayed.” After taking the flight controls the instructor observed that the airplane did not respond to pitch control inputs. The flight instructor was able to maneuver the airplane using the ailerons, rudder, full nose up pitch trim, and engine power. During the final approach to runway 01, the airplane lost altitude and impacted terrain, resulting in substantial damage to the airplane’s fuselage. Examination of the airplane revealed that the rear elevator control rod had fractured about three inches forward of the elevator quick disconnect. (See figure 1.) Figure 1: The separation in the rear elevator control rod, circled in yellow. According to maintenance records, the rear elevator control rod had been installed in December 2025 and had accrued 445 hours in service. The airplane wreckage was retained for further examination.
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
- Flight control sys malf/fail during initial climb defining event
The aircraft
- Airframe total time: 3,948.6 hours
- Last inspection: condition inspection, June 29, 2026
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
The flight
- Runway 01, 7,150 ft by 100 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 300° at 6 knots
- Visibility: 9 statute miles
- Sky: a few clouds
- Temperature: 97°F (36°C), dew point 61°F (16°C)
- Altimeter: 29.90 inHg
- Observation at 10:00 am from KGEU
Weather report (METAR): METAR KGEU 121647Z 30006KT 9SM CLR 36/16 A2990
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Other NTSB records under N126GX the same tail number, which may have belonged to a different aircraft at the time
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR26LA258.