DEN08LA065

NTSB accident investigation · Plocher SHA-Glasair · Telluride, CO · February 9, 2008

Accident · No injuriesLimited investigationFinal report
Date
February 9, 2008, 11:15 local (17:15 UTC)
Place
Telluride, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N315LPPlocher SHA-Glasair
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Day
Status
Completed · report April 30, 2008
Report
Approved by Office Director
Parties
FAA Flight Standards District Office
FAA report
20080209009779A
Case key
67689

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 improper flare and his failure to maintain aircraft control, resulting in the design stress limits of the nose gear being exceeded. Contributing factors in this accident was the excessive airspeed, the pilot-induced porpoise of the airplane, and the tailwind.

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: landing flareAircraft › Aircraft oper/perf/capability · Incorrect use/operationAll aircraft: 1,285 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotAll aircraft: 9,295 casesProbable cause
Performance/control parameters: airspeedAircraft › Aircraft oper/perf/capability · Incorrect use/operationAll aircraft: 1,681 casesProbable cause
Action: incorrect action performancePersonnel issues › Action/decision · PilotAll aircraft: 1,386 casesProbable cause
Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Not specifiedAll aircraft: 594 casesProbable cause
AircraftAircraft › Aircraft structures · Capability exceededAll aircraft: 72 casesProbable cause

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.

Hard landingLanding-flare/touchdownAll aircraft: 2,102 casesDefining event

Analysis

Unicom advised the pilot that the winds were from 260 degrees at 6 knots. He decided to land on runway 09 as per the airport's request to avoid flying over populated areas. He postponed dropping his flaps until he "had the runway made." This resulted in a 90 knot airspeed, "which is a little high," and he crossed the runway threshold at 50 feet agl (above ground level). Full flaps were deployed and he reduced airspeed as he approached the runway. He noticed his groundspeed "was quite a bit higher than what [he] was accustomed to." The first touchdown was 800 feet past the runway threshold and as he pulled back to flare, the airplane ballooned up 20 feet. The pilot flared again but the airplane dropped and bounced on the main gear, then the nose gear, which then collapsed. The propeller struck the runway and the airplane skidded to a halt.

Factual narrative

On February 9, 2008, approximately 1115 mountain daylight time, a Plochar SHA-Glasair, N315LP, registered to and operated by the pilot, was substantially damaged during a hard landing at Telluride Regional Airport (TEX), Telluride, Colorado. Visual meteorological conditions (VMC) prevailed at the time of the accident. The personal flight was being conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91 without a flight plan. The private pilot, the sole occupant aboard, was not injured. The cross-country flight originated at Boise (BOI), Idaho, approximately 0800, and was en route to TEX.

The pilot told an FAA inspector that he landed "hot" and hard in a slight tailwind. The airplane began to porpoise. The nose wheel broke off and the airplane skidded to a halt. The airplane was transported back to BOI where a mechanic, who examined the airplane, reported finding significant damage to the composite structure.

According to the pilot's accident report, the wind was initially reported to be calm, so he planned on landing on runway 09 as per the airport's request to avoid flying over populated areas. As he got closer to the airport, TEX Unicom advised that the winds were from 260 degrees at 6 knots. He decided to postpone dropping his flaps until he "had the runway made." This resulted in a 90 knot airspeed, "which is a little high," and he crossed the runway threshold at 50 feet agl (above ground level). Full flaps were deployed and he reduced airspeed as he approached the runway. He noticed his groundspeed "was quite a bit higher than what [he] was accustomed to." The first touch down was 800 feet past the runway threshold and as he pulled back to flare, the airplane ballooned up 20 feet. The pilot flared again but the airplane dropped and bounced on the main gear, then the nose gear, which then collapsed. The propeller struck the runway and the airplane skidded to a halt.

According to the pilot's accident report, he had logged 73 total flight hours, of which 22 hours were in the Glasair.

Aircraft

Registration
N315LP
Reported as
Plocher SHA-Glasair
Category
Airplane, amateur-built
Serial number
315
Airframe hours
700
Engine
Lycoming IO-320-E1A, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Jon D. Biggs
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Annual · August 1, 2007 · 22 hours before
Departed
BOI · Boise, ID
Destination
TEX · Telluride, CO
Airport
TEX · Telluride, runway 09, 6,870 × 100 ft, asphalt

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
44
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Seat
Left
Flight hours
73 total · 22 in this make and model · 35 as pilot in command · 16 in the last 90 days · 7 in the last 30 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Temperature
32 °F, dew point 45 °F
Altimeter
30.18 inHg
Observed at
TEX

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.