WPR24FA213 · Grumman Acft ENG COR-Schweizer G-164A
Nor Wes Grumman Acft ENG COR-Schweizer G-164A · Accident
From Doña Ana County International Jetport (DNA) to an unrecorded destination
Event
- NTSB case
- WPR24FA213
- 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
Grumman Acft ENG COR-Schweizer G-164A
- Aircraft type
- Grumman G-164
- 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
- N9709
- Operator
- Nor Wes
- Onboard fatalities
- Unknown
- Route
- From Doña Ana County International Jetport (DNA), Santa Teresa, NMTo not recorded
- Aircraft age
- About 50 years (built 1974)
- 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
- Unknown
- 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
- Unknown or undetermined
- 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
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Before the accident pilot departed on his first solo flight in the single-seat, turbopropeller-equipped biplane, the chief pilot instructed him to depart to the north, climb to altitude, practice turns, climbs and descents, and then return to the departure airport. The chief pilot and the accident pilot were unable to communicate via radio and instead exchanged several text messages during the flight. The accident pilot sent a message stating, “it shakes a little bit, I don’t know if its normal,” to which the chief pilot replied, “Yeah it’s just a lot of horsepower on the front of the plane.” There were no further communications from the accident pilot. Shortly thereafter, the chief pilot observed smoke rising from the area where the pilot was operating. He departed in another airplane and subsequently located the accident site. Two witnesses saw the airplane flying low from north to south. Both witnesses reported that the engine sounded normal. One witness stated that he saw the airplane’s wings rocking left and right several times. The airplane came to rest in sandy desert terrain and was largely consumed by a postimpact fire. No ground scars were observed near the accident site. All major components of the airplane were present, and impact damage was consistent with a right-wing-low, nose-down pitch attitude at the time of impact. Control continuity was established for the left and right lower wing flaperons from the cockpit to the control surfaces. Rudder control continuity was established from the cockpit to the rudder. Elevator control continuity could not be confirmed due to impact and thermal damage. Postaccident examination of the propeller revealed operational signatures consistent with low-to-moderate engine power. Postaccident examination of the engine revealed evidence consistent with the engine producing power at the time of impact, with no indications of preimpact mechanical malfunctions or failures that would have precluded normal operation. Review of the airplane’s maintenance records indicated that its most recent annual inspection was 13 months before the accident. The airplane was issued a special flight permit 20 days before the accident that was valid for 10 days and allowed the airplane to be ferried for repairs or maintenance. The chief pilot reported that the accident flight was the airplane’s first flight following maintenance and that the mechanic had not completed a logbook entry. The mechanic who performed the maintenance stated that she had started the airplane’s annual inspection but did not complete it, because the owner wanted to fly the airplane. When asked, the chief pilot stated that he made the decision to fly the airplane. Review of records provided by the operator after the accident revealed a new entry for an annual inspection, dated the day of the accident. Review of the pilot’s logbook indicated that, in the months before the accident, he received agricultural application training in several models of tailwheel-equipped airplanes, including a high performance, piston-engine-powered biplane; however, other than referring to “chair flights” performed before the accident flight, the operator did not provide additional information regarding the pilot’s transition training for the turbine-powered accident airplane. The orientation of the airplane at the accident site and the lack of ground scarring around the wreckage was consistent with the nose-low, near-vertical descent characteristic of an aerodynamic stall; however, the reason for the loss of control could not be determined based on the available information. Although examination of the wreckage did not reveal any mechanical malfunctions or anomalies, the scope of the examination was limited due to the thermal damage sustained during the postcrash fire. Given the pilot’s unfamiliarity with the accident airplane, it is possible that attempting to communicate with the chief pilot via text message during the flight provided an additional distraction that may have contributed to the loss of control.
Probable cause
An aerodynamic stall and loss of control for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA213
- Event ID
- 20240625194549
- Case number
- WPR24FA213
- 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: fd4f005a87ba19dbbbf1e1a224af4f3776aad71ef4a59ce9440a46b299d30e9c; retrieved 2026-09-15T08:19:30.067Z.