CEN11CA560 · Cessna 182S
Phoenix Flyers Cessna 182S · Accident: abnormal runway contact during takeoff
From Las Cruces International Airport (LRU) to Phoenix Deer Valley Airport (KDVT)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11CA560
- 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
- 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 182S
- 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
- N493JL
- Operator
- Phoenix Flyers
- Onboard fatalities
- Unknown
- Route
- From Las Cruces International Airport (LRU), Los Cruces, NMTo Phoenix Deer Valley Airport (KDVT), Phoenix, AZ
- 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
- Takeoff · rejected takeoff
- Defining eventThe 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, during takeoff the airplane's airspeed was not increasing above 40 knots and he elected to abort the takeoff. The pilot pulled back on the control yoke to slow down and applied the brakes. The airplane bounced two or three times, and then the landing gear collapsed and the propeller struck the runway, resulting in substantial damage to the firewall. Witnesses reported that the airplane was approximately 30 to 40 feet above the ground before it descended back to the runway and bounced three times. A Federal Aviation Administration (FAA) inspector calculated the density altitude as 7,700 feet and the weight of the airplane near the maximum takeoff weight. The FAA inspector confirmed that there were no mechanical anomalies or failures with the airplane, engine, or related systems prior to the accident.
Probable cause
The pilot's loss of aircraft control due to insufficient aircraft performance during takeoff, with a heavy gross weight and a high density altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA560
- Event ID
- 20110810X70754
- Case number
- CEN11CA560
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: da91d663a019f8672f79449e0be51b6ffa3a89cf916b3695862fda11f92da1f5; retrieved 2026-09-15T16:35:31.340Z.