# NTSB NYC08CA284: Ferree Prostar B, N20HU, Salisbury, MD, August 20, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 20, 2008, 12:40 local (16:40 UTC) - Place: Salisbury, MD - Coordinates: 38.340278, -75.510276 - Nearby events: https://openairdocs.org/map.md?lat=38.3403&lon=-75.5103&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 22, 2009 - Report: Approved by Office Director - Parties: FAA FSDO - NTSB case key (mKey): 68751 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC08CA284 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68751/pdf - Page: https://openairdocs.org/ntsb/NYC08CA284 ## Probable cause The pilot's improper flare which resulted in a hard landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Ferree Howard B PRO STAR-B, 1 case](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=05626TU), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Ferree Howard B PRO STAR-B, 1 case](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=05626TU), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Ferree Howard B PRO STAR-B, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=05626TU), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The pilot/owner/builder of the experimental amateur-built Prostar B was completing his first traffic pattern of the day, which was also the airplane's fourth flight. While on final approach for landing on Runway 23, the airplane's alignment was "a little left of centerline." The pilot adjusted the airplane's alignment with the runway, his airspeed "bled off" before the airplane "ballooned" and then dropped to the runway. The airplane experienced a hard landing, the main landing gear separated, and the airplane skidded to a stop on the runway. When asked about the performance and handling characteristics of the airplane, the pilot reported that the airplane was running fine, but that the left wing was "heavy" and that he had recently made rigging adjustments to correct it. Examination of the airplane by a Federal Aviation Administration inspector did not reveal any preimpact malfunctions. Winds reported at the airport were from 140 degrees at 5 knots. ## Factual narrative According to the pilot/owner/builder of the experimental amateur-built Prostar B, he was completing his first traffic pattern of the day, which was also the airplane's fourth flight. While on final approach for landing on Runway 23, the airplane's alignment was "a little left of centerline." The pilot said that as he adjusted the airplane's alignment with the runway, his airspeed "bled off" before the airplane "ballooned" and then dropped to the runway. The airplane experienced a hard landing, the main landing gear separated, and the airplane skidded to a stop on the runway. When asked about the performance and handling characteristics of the airplane, the pilot reported that the airplane was running fine, but that the left wing was "heavy" and that he had recently made rigging adjustments to correct it. Examination of the airplane by a Federal Aviation Administration inspector did not reveal any preimpact malfunctions. Winds reported at the airport were from 140 degrees at 5 knots. ## Aircraft - Registration: [N20HU](https://openairdocs.org/deregistered/N20HU-2008-09-17), registration cancelled 2008-09-17, S/N PT1184, built 1998 (OpenAirDocs) - Reported make and model: Ferree Prostar B - Registry model: [Ferree Howard B PRO STAR-B](https://openairdocs.org/model/ferree-howard-b-pro-star-b) (registry code 05626TU) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: PT1184 - Airframe hours: 12 - Engines: Lycoming O320-A2B 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Howard B. Ferree - Registered owner: Howard B. Ferree - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, June 1, 2008, 10 hours before - Departed: SBY, SALISBURY, MD - Destination: SBY, SALISBURY, MD - Airport: SBY, Salisbury-Wicomico County Regi, runway 23, 5,000 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 79; injuries: none; private; airplane ratings: single-engine land; medical: class 3; flight hours: 606 total, 12 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 140° at 5 knots - Visibility: 10 statute miles - Temperature: 79 °F, dew point 57 °F - Altimeter: 30.20 inHg - Observed at: SBY ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20080820846099A](https://openairdocs.org/incident/20080820846099A), Aug 20, 2008: PROSTARB, Salisbury, MD, Substantial damage. (-23) While on final approach, the pilot let the aircraft drift left of centerline to the runway. While trying to correct the flight path, he let the airspeed… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.