FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Amarillo Flying Service Cessna 182RG accident

1 Sept 1988 · ANTELOPE WELLS, NM, United States

Cessna 182RG · Accident: on ground/water collision with object during takeoff

From No airport to Deming Municipal Airport (DMN)

Report a problem

Event

NTSB case
DEN88LA196
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
Charter & commuter
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

Cessna 182RG

Aircraft type
Cessna 182
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
N3184C
Onboard fatalities
Unknown
Route
From No airportTo Deming Municipal Airport (DMN), Deming, NM
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 135: Air Taxi & Commuter
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
Takeoff · roll/run
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
On ground/water collision with object
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 › Unsuitable terrain or takeoff/landing/taxi area, selected
  • Pilot in command › Visual lookout, not maintained

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

NTSB narrative

THE COMMERCIAL PLT WAS FLYING THREE PASSENGERS TO BUY CATTLE. DURING TAKEOFF FROM A 5,000 X 75 FT, WET GRAVEL AIRSTRIP, THE PLT ELECTED TO USE ONLY THE LEFT SIDE OF THE RWY TO AVOID MUD. HE USED A SOFT FIELD TAKEOFF, WITH A NOSE HIGH ATTITUDE, WHICH LIMITED HIS FORWARD VISIBILITY. HE DID NOT NOTICE SEVERAL PILES OF GRAVEL ALONG THE LEFT SIDE OF THE RWY. JUST PRIOR TO LIFTOFF, THE LEFT MAIN GEAR HIT A PILE OF GRAVEL AND THE ACFT TURNED LEFT, DEPARTING THE RWY. THE UNDERSIDE OF THE FUSELAGE HIT ANOTHER PILE OF GRAVEL AND TORE A 3 FT LONG HOLE IN THE FUSELAGE. THE PILOT ABORTED THE TAKEOFF AND TAXIED BACK TO THE STARTING POINT. AFTER THE ACCIDENT THE PILOT NOTED THAT THE LEFT MAIN GEAR WAS PUSHED BACK AND THE GEAR MOUNT WAS DAMAGED. THE FUSELAGE WAS EXTENSIVELY WRINKLED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN88LA196
Event ID
20001213X26809
Case number
DEN88LA196
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: c3dd7b279ffff28ae51c00b8bfcabf920626e10f839fc1b81ab8370e5dec0c94; retrieved 2026-09-18T19:19:07.411Z.