GAA16CA315

NTSB accident investigation · Seela Gerald L Glasair SH 2F · State College, PA · June 8, 2016

Accident · No injuriesData collectionFinal report
Date
June 8, 2016, 13:25 local (17:25 UTC)
Place
State College, PA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N666GJSeela Gerald L Glasair SH 2F
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report October 27, 2016
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160608009219A
Case key
93382

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 hard landing in gusting wind conditions. Contributing to the accident were the pilot's unfamiliarity with the newly purchased airplane's throttle resulting in an unstable approach, and the pilot's ability to compensate for the wind.

Findings · 6

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.

Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedSeela Gerald L GLASAIR SH-2F: 1 caseAll aircraft: 809 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Ability to respond/compensateSeela Gerald L GLASAIR SH-2F: 1 caseAll aircraft: 1,199 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Decision related to conditionSeela Gerald L GLASAIR SH-2F: 1 caseAll aircraft: 1,199 cases
Wind: crosswindEnvironmental issues › Conditions/weather/phenomena · Ability to respond/compensateSeela Gerald L GLASAIR SH-2F: 1 caseAll aircraft: 1,008 cases

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 was returning to his home airport after purchasing the accident airplane, but prior to returning home, the pilot had received a two hour checkout in the airplane. Upon arrival, the weather had deteriorated, rain made it hard to see and the wind was gusting. The pilot reported that he had to go around during the first landing due to the wind. He reported that during the second landing he undercompensated for the wind and the airplane landed hard, bounced and touched down again off the left side of the runway. The airplane sustained substantial damage to the fuselage. The pilot reported that during both approaches he had trouble manipulating the throttle; it appeared to stick and unstick at times making engine performance and power application erratic, resulting in an unstabilized approach, and compensation for the gusting wind difficult. The wind at the airport at the time of the accident was reported as 310 degrees true, 18 knots, with gusts to 35 knots. The pilot landed runway 24, and reported that he should have chosen another airport with a crosswind runway. Further, following the accident, the pilot realized that he was not familiar enough with the airplane's Vernier type throttle, as his past experience was with a lever type throttle. An FAA inspector who examined the airplane after the accident reported that the Vernier throttle operated normally.

Factual narrative

According to the pilot, he was returning to his home airport after purchasing the accident airplane, but prior to returning home, the pilot had received a two hour checkout in the airplane. Upon arrival, the weather had deteriorated, rain made it hard to see and the wind was gusting. The pilot reported that he had to go around during the first landing due to the wind. He reported that during the second landing he undercompensated for the wind and the airplane landed hard, bounced and touched down again off the left side of the runway. The airplane sustained substantial damage to the fuselage. The pilot reported that during both approaches he had trouble manipulating the throttle; it appeared to stick and unstick at times making engine performance and power application erratic, resulting in an unstabilized approach, and compensation for the gusting wind difficult. The wind at the airport at the time of the accident was reported as 310 degrees true, 18 knots, with gusts to 35 knots. The pilot landed runway 24, and reported that he should have chosen another airport with a crosswind runway. Further, following the accident, the pilot realized that he was not familiar enough with the airplane's Vernier type throttle, as his past experience was with a lever type throttle. An FAA inspector who examined the airplane after the accident reported that the Vernier throttle operated normally.

Aircraft

Registration
N666GJ
Reported as
Seela Gerald L Glasair SH 2F (FT)
Category
Airplane, amateur-built
Serial number
666
Built
1989
Airframe hours
1,316
Engine
Lycoming O-320, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Condition · May 1, 2016
Departed
HTS · Huntington, WV
Destination
UNV · State College, PA
Airport
UNV · University Park, runway 24, 6,701 × 150 ft, asphalt
Equipment
Auto-pilot, 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
70
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
250 total · 3 in this make and model · 14 as pilot in command · 5 in the last 90 days · 5 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
310° at 18 knots, gusting 35
Visibility
10 statute miles
Lowest ceiling
7,000 ft broken
Temperature
54 °F, dew point 45 °F
Altimeter
29.81 inHg
Observed at
KUNV

Docket · 3

The files NTSB released with the investigation on September 26, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 676 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.