NTSB CAROL · Event
Event DEN04LA007
Registry · N331DM
FAA Aircraft Registry record.
Make / Model
DASSAULT/SUD FAN JET FALCON SER F
Year of manufacture
1982 · 21 years old at event
Engine
AMA/EXPR UNKNOWN ENG
Seats / Engines
14 seats · 2 engines
Last airworthiness date
19920814
ADS-B equipped
Yes — Mode-S A399DD
Registrant of record
HT AIR LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the instructor's improper in-flight planning/decision making and fuel mismanagement which resulted in fuel starvation/exhaustion, the loss of engine power and the subsequent forced landing. Contributing factors include the instructor's inadequate preflight planning/preparation and the lack of suitable terrain for a forced landing.
Factual narrative
On October 11, 2003, at 0835 mountain daylight time, an Aviat, Inc., Pitts S2B, N331DM, was substantially damaged when it impacted terrain during a forced landing near Dona Ana County at Santa Teresa Airport (5T6), Santa Teresa, New Mexico. The airline transport certificated flight instructor, and the private pilot receiving instruction were not injured. Visual meteorological conditions prevailed. No flight plan had been filed for the local instructional flight being conducted under the provisions of Title 14 CFR Part 91. The flight originated at 0808. According to the instructor, he was giving instruction to the private pilot who had recently purchased the airplane. They departed 5T6 with approximately 15 gallons of fuel. After completing four touch-and-go landings, they departed the pattern to do some air work, which included steep turns and a stall. At 3,500 feet agl, approximately 3 to 4 miles north of the airport, the engine lost all power. The instructor stated that he was unable to reach the airport using "best glide." The instructor made a forced landing in a field approximately 1/2 mile east-northeast of the approach end of runway 28. When the airplane impacted the ground, both the left and right main landing gear assemblies collapsed, the upper wing assembly was displaced aft, and the lower left wing, left horizontal stabilizer, and elevator were buckled. According to an airport employee, who gave the instructor and private pilot a ride back to the hanger, the instructor stated that the airplane's engine stalled and they had to land in the desert. The instructor also stated that he thought there may have been some water in the fuel. The private pilot asked the airport employee if he could borrow a vehicle to go back to the airplane to get their gear. The private pilot also asked the airport employee if he could purchase 5 gallons of fuel. According to the airport manager, the airport vehicle that the private pilot borrowed was equipped to use a special 100 octane Low Lead fuel that is color-coded red, instead of blue, to indicate it is for vehicle usage and not for aviation. At 0930, the private pilot purchased 5 gallons of 100 low-lead fuel. The fuel purchased, was logged as fuel for N331DM. The fuel was dispensed from the 100 Octane Low Lead aviation fuel tank, into a 5-gallon fuel can. According to an FAA inspector, on November 17, 2003, during a telephone conversation with the instructor, the instructor stated that he did not believe the owner had ever purchased fuel for the airplane. The FAA inspector informed the instructor that prior to selling the airplane, the previous owner fueled the airplane and then logged 0.7 hours of flight time and the instructor and private pilot had logged 0.8 hours of flight time. The airplane's records indicated a total of 1.5 hours of flight time since the airplane was last fueled. The instructor agreed that N331DM's fuel burn rate would be approximately 15 gallons per hour for a total of approximately 22.5 gallons, which was close to the airplane's useable fuel quantity of 23 gallons. The instructor was told of evidence indicating that the private pilot had purchased 5 gallons of fuel after the accident. The instructor stated that "he never goes into the desert without extra fuel." The instructor also stated that it took them a "couple of hours" to locate the airplane. According to an FAA inspector, on November 17, 2003, during a telephone conversation with the private pilot, the private pilot stated that he never purchased fuel for the airplane. The private pilot was told of evidence indicating that he had purchased 5 gallons of fuel after the accident. The private pilot stated that "he never saw where that fuel went." The private pilot stated that he thought the fuel was for the vehicle, but he never saw anyone put fuel into the vehicle. The private pilot also stated that he never saw anyone put fuel into the airplane, as "it sure as hell wasn't going to fly out of there." An FAA inspector, who examined the airplane, stated that there was approximately 4 inches of fuel remaining in the airplane's main fuel tank and no fuel in the wing tank. He also stated that the airplane's maintenance records were examined, and an engine test run was completed. There were no pre-impact deficiencies noted that would have precluded normal engine operation. According to the instructor, he was giving instruction to the private pilot who had recently purchased the airplane. They departed with approximately 15 gallons of fuel. After completing four touch-and-go landings, they departed the pattern to do some air work, which included steep turns and a stall. At 3,500 feet agl, approximately 3 to 4 miles north of the airport, the engine lost all power. The instructor stated that he was unable to reach the airport using "best glide." The instructor made a forced landing in a field approximately 1/2 mile east-northeast of the approach end of runway 28. When the airplane impacted the ground, both the left and right main landing gear assemblies collapsed, the upper wing assembly was displaced aft, and the lower left wing, left horizontal stabilizer, and elevator were buckled. An examination of the airplane revealed 4 inches of fuel in the airplane's main fuel tank and no fuel in the wing tank. No other anomalies were found. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_DEN04LA007.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, fuel starvation, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗