- Date
- November 28, 2015, 13:00 local (18:00 UTC)
- Place
- Salisbury, NC
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N2000RCessna 182
- Defining event
- Landing-flare/touchdown: Hard landing
- Weather
- Visual (VMC) · Day
- Status
- Completed · report April 5, 2016
- Report
- Approved by Office Director
- NTSB office
- General Aviation Accidents
- Parties
- Federal Aviation Administration
- FAA report
- 20151128021139A
- Case key
- 92455
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot's failure to maintain pitch control during the landing flare, causing the airplane to balloon and land hard.
Findings · 4
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
According to the pilot of the tricycle landing gear equipped airplane, he was performing skydiving operations. He reported that he felt rushed in performing his assigned duties because, "the skydiving school kept wanting me to return quicker for the next load." The pilot recalled that after dropping the sky divers, he made his approach to land; the airplane ballooned during the flare, and landed hard on all three landing gear. The airplane sustained substantial damage to the firewall. The pilot reported that there were no mechanical failures or anomalies prior to or during the flight that would have prevented normal flight operation.
Factual narrative
According to the pilot of the tricycle landing gear equipped airplane, he was performing skydiving operations. He reported that he felt rushed in performing his assigned duties because, "the skydiving school kept wanting me to return quicker for the next load." The pilot recalled that after dropping the sky divers, he made his approach to land; the airplane ballooned during the flare, and landed hard on all three landing gear. The airplane sustained substantial damage to the firewall. The pilot reported that there were no mechanical failures or anomalies prior to or during the flight that would have prevented normal flight operation.
Aircraft
- Registration
- N2000R
- Reported as
- Cessna 182 (G)
- Category
- Airplane
- Serial number
- 18255200
- Built
- 1963
- Airframe hours
- 6,934
- Engine
- Cont Motor O-470-R, 230 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Skydiving · Part 91
- Operator
- Piedmont Skydiving Center LLC
- Registered owner
- Piedmont Skydiving Center LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · November 6, 2015
- Departed
- RUQ · Salisbury, NC
- Destination
- RUQ · Salisbury, NC
- Airport
- RUQ · Rowan County, runway 20, 5,501 × 100 ft, asphalt
- Equipment
- Stall warning system, Handheld GPS
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 49
- Injuries
- None
- Certificates
- Commercial, Flight engineer
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 1, With waivers/limitations
- Last flight review
- November 19, 2015
- Seat
- Left
- Restraint
- Lap only
- Flight hours
- 406 total · 11 in this make and model · 321 as pilot in command · 51 in the last 90 days · 29 in the last 30 days · 10 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 250° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 64 °F, dew point 52 °F
- Altimeter
- 30.26 inHg
- Observed at
- KRUQ
Docket · 2
The files NTSB released with the investigation on March 10, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.1 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.