# NTSB LAX08CA248: Bristol Titan Tornado II, N25JT, Green River, UT, July 30, 2008

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: July 30, 2008, 09:30 local (15:30 UTC)
- Place: Green River, UT
- Coordinates: 38.961387, -110.2275
- Nearby events: https://openairdocs.org/map.md?lat=38.9614&lon=-110.2275&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Defining event: [Enroute-cruise: Miscellaneous/other](https://openairdocs.org/ntsb-events/900)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report September 26, 2008
- Report: Approved by Office Director
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 68566
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX08CA248
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68566/pdf
- Page: https://openairdocs.org/ntsb/LAX08CA248

## Probable cause

The encounter with rough terrain during an off-field precautionary landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Physical workspace: warnings/alarms](https://openairdocs.org/ntsb-findings/03041055): Environmental issues › Task environment · Decision related to condition; cases with it: [Bristol Todd J TITAN TORNADO II, 1 case](https://openairdocs.org/ntsb-findings/03041055/cases.md?model=0590213), [All aircraft, 2 cases](https://openairdocs.org/ntsb-findings/03041055/cases.md)
- [Terrain: rough terrain](https://openairdocs.org/ntsb-findings/03021015): Environmental issues › Physical environment · Not specified (probable cause); cases with it: [Bristol Todd J TITAN TORNADO II, 1 case](https://openairdocs.org/ntsb-findings/03021015/cases.md?model=0590213), [All aircraft, 442 cases](https://openairdocs.org/ntsb-findings/03021015/cases.md)
- [Runway/land/takeoff/taxi surface](https://openairdocs.org/ntsb-findings/03023000): Environmental issues › Physical environment · Not specified (probable cause); cases with it: [Bristol Todd J TITAN TORNADO II, 1 case](https://openairdocs.org/ntsb-findings/03023000/cases.md?model=0590213), [All aircraft, 253 cases](https://openairdocs.org/ntsb-findings/03023000/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Enroute-cruise: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Bristol Todd J TITAN TORNADO II, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=0590213), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Bristol Todd J TITAN TORNADO II, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=0590213), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot reported that 3 weeks prior to the accident he had taken delivery of the newly purchased airplane, and he proceeded to receive approximately 10 hours of flight instruction in it.  He intended to fly the airplane cross-country back to his home. While en route, an unlabeled red light illuminated on the instrument panel.  He checked his Electronic Flight Information System (EFIS) panel and found nothing abnormal. Concerned that the light may indicate low oil pressure, the pilot performed a precautionary landing on to a narrow gravel path.  During the landing, the airplane impacted a stone on the path and bounced off the steeply banked path into the sand below.  The airplane then nosed over.  According to the builder, the red light was part of the Electronic Flight Information System (EFIS).  If a parameter monitored by the EFIS is outside of set limits, then the red light on the instrument panel will illuminate and the parameter that is out of limits will display on the EFIS screen.  The parameters monitored by the EFIS are engine rpm, fuel quantity, exhaust gas temperature, oil temperature and pressure, and cylinder head temperature.  Other items monitored by the EFIS are engine operating times, and scheduled maintenance information messages.  The pilot did not report finding any anomalies with the airplane or engine.

## Factual narrative

On July 30, 2008, at 0930 mountain daylight time, a Bristol Titan Tornado II, N25JJ, collided with terrain while attempting a precautionary landing near Green River, Utah.  The commercial pilot operated the experimental category light-sport airplane under the provisions of Title 14 of the Code of Federal Regulations, Part 91.  The pilot was not injured, and the airplane was substantially damaged.  Visual meteorological conditions prevailed, and no flight plan had been filed.  The flight originated at Cedar City, Utah, about 0700.

The pilot reported that 3 weeks prior to the accident he had taken delivery of the airplane, and he proceeded to receive approximately 10 hours of flight instruction in the airplane.  He intended to fly the airplane cross-country back to his home.  He took off from Cedar City, and while en route to Nephi, Utah, an unlabeled red light illuminated on the instrument panel.  He checked his Electronic Flight Information System (EFIS) panel and found nothing abnormal. Concerned that the light may indicate low oil pressure, the pilot performed a precautionary landing on to  a narrow gravel path.  During the landing, the airplane impacted a stone and bounced off the steeply banked path into the sand below.

The builder of the airplane related to the National Transportation Safety Board investigator that the red light was part of the EFIS.  If a parameter monitored by the EFIS is outside its set limits, then the red light on the instrument panel will illuminate and the parameter that is out of limits will display on the EFIS screen.  The parameters monitored by the EFIS are engine rpm, fuel quantity, exhaust gas temperature, oil temperature and pressure, and cylinder head temperature.  Other items monitored by the EFIS are engine operating times, and scheduled maintenance information messages.

## Aircraft

- Registration: [N25JT](https://openairdocs.org/deregistered/N25JT-2015-05-19), registration cancelled 2015-05-19, S/N T98503COHK0293, built 2001 (OpenAirDocs)
- Reported make and model: Bristol Titan Tornado II
- Registry model: [Bristol Todd J TITAN TORNADO II](https://openairdocs.org/model/bristol-todd-j-titan-tornado-ii) (registry code 0590213) (OpenAirDocs)
- Registry engine: [Jabiru 2200](https://openairdocs.org/engine/jabiru-2200) (registry code 34800, 4 cycle) (OpenAirDocs)
- Category: Airplane
- Serial number: T98503COHKo293
- Engines: Jabiru 2200 reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Trevor Melia
- Airworthiness certificate: Special, Special light-sport (Special); Special, Experimental (Special)
- Departed: KCDQ, Cedar City, UT
- Destination: KU14, Nephi, UT

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 75; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3; flight hours: 1,000 total, 20 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 90 °F

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20080730841649A](https://openairdocs.org/incident/20080730841649A), Jul 30, 2008: Amtr TITANTORNADO, Green River, UT, Substantial damage. (-23) The pilot said that he departed cedar city at about 0700 after some time he noticed that a red light was blinking indicating that some engine parameter…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
