FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08FA023 · Cessna T182T

8 Nov 2007 · Las Vegas, NV, United States

Cessna T182T · Accident: in flight collision with terrain/water en route

From North Las Vegas Airport (VGT) to Rosamond Skypark Airport (L00)

Report a problem

Event

NTSB case
SEA08FA023
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
2 · all aircraft and ground
Ground fatalities
Unknown
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

Cessna T182T

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
N881CP
Operator
Dion J. DeCamp · private individual
Onboard fatalities
Unknown
Route
From North Las Vegas Airport (VGT), Las Vegas, NVTo Rosamond Skypark Airport (L00), Rosamond, CA
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
En route · climb to cruise
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
In flight collision with terrain/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

"THIS CASE WAS MODIFIED JANUARY 27, 2009."

The airplane collided with rising mountainous terrain during climb to cruise about 21 nm southwest of the departure airport. The accident occurred during dark night, visual meteorological conditions, about 13 minutes into the night cross-country flight. No lighted roads or round structures were present in the area to provide ground reference to terrain. 1% of the moons disk was illuminated. Over the last 6 minutes of the flight, recorded radar data indicated the airplane's average groundspeed was 100 knots and its average rate of climb was 406 fpm; an average rate of climb of 600 fpm was required to clear terrain along the flight path. An examination of the accident site indicated that the airplane impacted rapidly rising terrain in a near level flight attitude before descending and coming to rest in a rock outcropping. The resultant high-energy impact forces, coupled with the extensive thermal damage, destroyed the airplane. A postaccident examination of the airframe's structure and engine failed to reveal any preimpact failures or malfunctions. The airplane was equipped with a Garmin G1000 Integrated Cockpit System, which incorporates a multifunction color display that is capable of displaying terrain elevation information when selected to the Terrain Proximity page. Due to the extensive impact and thermal damage that the component had sustained, it was not possible to determine if the pilot was using the display to receive topographic data during the airplane's ascent. Records indicate that the pilot had received G1000 training. The Pilot's Guide for the G1000 states: "CAUTION: Use of Terrain Proximity information for primary terrain avoidance is prohibited. The Terrain Proximity Map is intended only to enhance situational awareness. It is the pilot's responsibility to provide terrain avoidance at all times." The flight was departing on a VFR flight plan and was receiving VFR flight following services from the Las Vegas Terminal Radar Approach Control facility. Air traffic control radar data revealed that the airplane was continuously visible to the controller on his radar display from the departure airport until impact with mountainous terrain. The airplane's course remained constant as he approached and impacted the mountain during the dark nighttime flight. The air traffic controller did not issue a terrain-related safety alert, as required by a Federal Aviation Administration order, because he did not observe a conflict with terrain.

Probable cause

The pilot's failure to maintain an adequate terrain clearance/altitude during climb to cruise. Contributing to the accident were rising mountainous terrain, the dark nighttime lighting condition, the pilot's loss of situational awareness, and the Federal Aviation Administration controller's failure to issue a terrain-related safety alert.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08FA023
Event ID
20071121X01832
Case number
SEA08FA023
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2007-11-09.
  • API snapshot SHA-256: 9885ce39f31b4f4a0e80a27107cb660204130d752af1d7fdf8438f0a5f79f78b; retrieved 2026-09-20T16:07:02.155Z.