- Date
- April 2, 2011, 17:15 local (21:15 UTC)
- Place
- Factoryville, PA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N7225XCessna 150A
- Defining event
- Landing-flare/touchdown: Hard landing
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 20, 2011
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20110402004739A
- Case key
- 78769
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 inadequate flare during the gusty crosswind landing, which resulted in a hard landing.
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, he approached runway 4 once and performed a go-around due to the wind conditions. The second approach to the runway was higher than usual; therefore, the pilot increased the rate of descent in order to land in the crosswind and gusting wind conditions. The airplane impacted the runway and bounced, veered off the side of the runway, and came to rest in the reverse direction of travel. The accident sequence resulted in substantial damage to the right wing and fuselage. The pilot reported there were no mechanical anomalies with the airplane. The wind reported at an airport 15 miles south of the accident location, about the time of the accident, was from 330 degrees at 10 knots, gusting to 16 knots.
Factual narrative
According to the pilot, he approached runway 4 once and performed a go-around due to the wind conditions. The second approach to the runway was higher than usual; therefore, the pilot increased the rate of descent in order to land in the crosswind and gusting conditions. The airplane impacted the runway and bounced, then veered off the side of the runway, and came to rest in the reverse direction of travel. The accident sequence resulted in substantial damage to the right wing and fuselage. The pilot reported there were no mechanical anomalies with the airplane. The winds reported at an airport 15 miles south of the accident location, about the time of the accident, were from 330 degrees at 10 knots, gusting to 16 knots.
Aircraft
- Registration
- N7225X
- Reported as
- Cessna 150A
- Category
- Airplane
- Serial number
- 15059325
- Airframe hours
- 2,195
- Engine
- Cont Motor O-200 SERIES, 100 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Cessna N7225X LLC
- Registered owner
- Cessna N7225X LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · June 1, 2010
- Departed
- AVP · Scranton, PA
- Destination
- 9N3 · Factoryville, PA
- Airport
- 9N3 · Seamans Field, runway 04, 2,500 × 50 ft, asphalt
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
- 63
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, With waivers/limitations
- Last flight review
- November 23, 2010
- Seat
- Left
- Flight hours
- 110 total · 94 in this make and model · 16 as pilot in command · 16 in the last 90 days · 3 in the last 30 days · 3 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 330° at 10 knots, gusting 16
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 48 °F, dew point 25 °F
- Altimeter
- 29.54 inHg
- Observed at
- AVP, 15 nm away
Docket · 4
The files NTSB released with the investigation on April 18, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 800 KB 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.