FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN00LA014 · Piper PA-18-150

2 Nov 1999 · BULLFROG, UT, United States

Piper PA-18-150 · Accident: loss of control on ground/water during landing

From Canyonlands Regional Airport (CNY) to U07

Report a problem

Event

NTSB case
DEN00LA014
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
0 · all aircraft and ground
Ground fatalities
0
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

Piper PA-18-150

Aircraft type
Piper PA-18
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
N4285Z
Operator
James M. Elegante · private individual
Onboard fatalities
Unknown
Route
From Canyonlands Regional Airport (CNY), Moab, UTTo U07
Aircraft age
Not recorded
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
Landing · landing roll
First occurrenceThe 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
Loss of control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Directional control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot's landing on runway 19 was normal and the wind was calm. During landing roll, the aircraft departed the runway to the right, traveled down a 10 degree embankment and struck a fence. The pilot said he applied left rudder pressure without effect. According to an FAA inspector who interviewed the pilot following the accident, the pilot told him that he may have inadvertently applied pressure to the rudder pedal rather than to the brake. A functional test of the rudder and brake system was performed and no discrepancies were noted. The pilot had accumulated a total of 7 hours in the PA-18-150, 2 of which were as pilot-in-command. He had received his tailwheel endorsement on the day of the accident.

Probable cause

The pilot-in-command's failure to maintain directional control of the aircraft during landing roll. Factors were the pilot's lack of total experience in type of aircraft and the fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN00LA014
Event ID
20001212X20090
Case number
DEN00LA014
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 17c34056dc427b48c462ac8f9d18dcb48ff41e5f7ebc3b12cbf5562ebd997c5b; retrieved 2026-09-22T13:45:12.398Z.