4 Oct 2012: ERCOUPE 415-C

4 Oct 2012: ERCOUPE 415-C (N93606) — Unknown operator

No fatalities • Parkersburg, WV, United States

Probable cause

The student pilot’s improper landing flare, which resulted in a hard landing.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT

On October 4, 2012, about 1255 eastern daylight time, an Ercoupe 415-C, N93606, was substantially damaged during landing, at Mid-Ohio Valley Regional Airport (PKB), Parkersburg, West Virginia. The student pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the solo cross country instructional flight conducted under 14 Code of Federal Regulations Part 91, which departed Fairmont Municipal Airport (4G7), Fairmont, West Virginia.

According to the student pilot, the first leg of his solo cross country flight was uneventful until he attempted to land on runway 21 at PKB. During the flare, as the airplane began to settle, he reduced power and the airplane "dropped". It touched down on the main landing gear, then the nose landing gear and then "hopped". The airplane then "came back down", touched down again, rolled about 50 feet and the nose wheel separated from the nose landing gear. The airplane then slid to a stop, on the nose landing gear wheel fork.

PERSONNEL INFORMATION

According to Federal Aviation Administration (FAA) records, the student pilot was issued a student pilot certificate with third-class medical on February 14, 2012.

On April 30, 2012 the pilot received an endorsement to solo the Ercoupe 415-C, and on July 2, 2012, received an endorsement to make solo cross country flights.

AIRCRAFT INFORMATION

According to FAA and airplane maintenance records, the airplane was manufactured in 1946. The airplane’s most recent annual inspection was completed on March 14, 2012 and at the time of the inspection; the airplane had accrued 1,391 total hours of operation.

METEOROLOGICAL INFORMATION

The reported weather at PKB at 1253, included: winds from 230 degrees at 5 knots, 10 miles visibility, few clouds at 10,000 feet, temperature 23 degrees C, dew point 13 degrees C, and an altimeter setting of 30.20 inches of mercury.

AIRPORT INFORMATION

According to the Airport Facility Directory, PKB was controlled and had two runways oriented in a 03/21 and 10/28 configuration. Runway 21 was asphalt, grooved, and in good condition. It was 7,240 feet long and 150 feet wide. The threshold was displaced by 460 feet. The runway gradient was 0.7 percent and the runway was marked with precision markings.

WRECKAGE AND IMPACT INFORMATION

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that both halves of the two piece nose wheel assembly had separated from each other and multiple fractures existed in both halves. Further examination of the airplane also revealed that the firewall and fuselage had incurred substantial damage.

TESTS AND RESEARCH

The pilot did not report any mechanical problems prior to the landing but, he advised that due to the age of the airplane, the nose wheel assembly may have failed due to fatigue.

Examination of the nose wheel assembly by the NTSB's Materials Laboratory revealed however, that the damage was consistent with a hard landing, as two of the three mounting holes in the outer rim were cracked, the fracture faces on the wheel rims revealed rough grainy surfaces, and the bearing inner race surface was dimpled, displayed mechanical damage, and deformation of the bearing cage, seal, and retainer.

The locknuts were also ineffective and relatively old, and could be removed from the wheel bolts without the aid of tools. Only slight resistance could be felt as the bolt entered the locking portion of the locknut. The exterior surface of the locknuts was also corroded, and the locking portion of the locknuts displayed a full form thread similar to the metal threads.

Contributing factors

  • cause Incorrect use/operation
  • cause Student pilot

Conditions

Weather
VMC, wind 230/05kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.