- Date
- June 19, 2010, 14:20 local (20:20 UTC)
- Place
- Trinidad, CO
- Injuries
- 2 minor
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N134LSRemos G3/600
- Defining event
- Landing-landing roll: Collision with terr/obj (non-CFIT)
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 20, 2010
- Report
- Approved by Office Director
- NTSB office
- Central Region
- Parties
- FAA Flight Standards District Office
- FAA report
- 20100619037439A
- Case key
- 76358
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
A total loss of engine power in flight due to fuel exhaustion for unknown reasons.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
**This report was modified on 2/24/2011; please see the public docket on this accident for more information** After landing for fuel, the pilot noted that "the fuel gauge read slightly above 1/2 full." The airplane's fuel capacity is 20 gallons. He asked that 8 gallons of fuel be added; however, according to the fixed base operator’s records the airplane was serviced with only 6 gallons. En route to his destination, the pilot received flight following service from air traffic control (ATC). While enroute, the pilot told controllers that he was concerned about his fuel and inquired as to the fuel services nearby. He asked for and received vectors to a nearby airport. Unable to find the airport, the pilot tried unsuccessfully to contact ATC several times. The pilot then decided to make an off-airport landing. Another aircraft advised controllers that the pilot was making an emergency landing "due to fuel exhaustion." The pilot said that the engine lost power prior to landing. During the landing on rough terrain, the landing gear was sheared off from the composite fuselage. A Federal Aviation Administration (FAA) inspector questioned the pilot as to why he didn’t land for fuel at Raton, New Mexico. His reply was that he had never landed at that airport before and was unfamiliar with it. Asked if he had ever landed at Trinidad, the pilot said no. FAA inspectors who examined the airplane reported that the fuel quantity can either be checked with the fuel gauge or by examining the clear plastic tubing that shows the fuel level. An examination of the fuel gauge found it to be operating normally. No other anomalies were found; however, the engine manufacturer issued a mandatory Service Bulletin (SB) calling for replacement of the airplane's fuel pump. The SB notes that in limited cases a deviation in fuel supply can occur causing engine malfuntion or massive fuel leakage.
Factual narrative
**This report was modified on 2/24/2011; please see the public docket on this accident for more information** After landing for fuel, the pilot noted that "the fuel gauge read slightly above 1/2 full." The airplane's fuel capacity is 20 gallons. He asked that 8 gallons of fuel be added; however, according to the fixed base operator’s records the airplane was serviced with only 6 gallons. En route to his destination, the pilot received flight following service from air traffic control (ATC). While enroute, the pilot told controllers that he was concerned about his fuel and inquired as to the fuel services nearby. He asked for and received vectors to a nearby airport. Unable to find the airport, the pilot tried unsuccessfully to contact ATC several times. The pilot then decided to make an off-airport landing. Another aircraft advised controllers that the pilot was making an emergency landing "due to fuel exhaustion." The pilot said that the engine lost power prior to landing. During the landing on rough terrain, the landing gear was sheared off from the composite fuselage. A Federal Aviation Administration (FAA) inspector questioned the pilot as to why he didn’t land for fuel at Raton, New Mexico. His reply was that he had never landed at that airport before and was unfamiliar with it. Asked if he had ever landed at Trinidad, the pilot said no. FAA inspectors who examined the airplane reported that the fuel quantity can either be checked with the fuel gauge or by examining the clear plastic tubing that shows the fuel level. An examination of the fuel gauge found it to be operating normally. No other anomalies were found; however, the engine manufacturer issued a mandatory Service Bulletin (SB) calling for replacement of the airplane's fuel pump. The SB notes that in limited cases a deviation in fuel supply can occur causing engine malfuntion or massive fuel leakage.
Aircraft
- Registration
- N134LS
- Reported as
- Remos G3/600
- Category
- Airplane
- Serial number
- 215
- Airframe hours
- 271
- Engine
- Rotax 912ULS, 100 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- First Jet Now LLP
- Registered owner
- First Jet Now LLP
- Airworthiness certificate
- Special, Special light-sport (Special)
- Departed
- E80 · Belen, NM
- Destination
- COS · Colorado Sprngs, CO
- Flight plan
- VFR
- Airport
- TAD · Perry Stokes
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 71
- Injuries
- Minor
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, With waivers/limitations
- Seat
- Left
- Flight hours
- 537 total · 19 in this make and model · 297 as pilot in command
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 210° at 11 knots, gusting 19
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 95 °F, dew point 12 °F
- Altimeter
- 30.09 inHg
- Observed at
- TAD
Docket · 4
The files NTSB released with the investigation on August 16, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.2 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.