FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC08CA316 · Piper PA28-140

20 Sept 2008 · Carrabassett, ME, United States

Piper PA28-140 · Accident: hard landing

From Nashua Airport / Boire Field (ASH) to Sugarloaf Regional Airport (B21)

Report a problem

Event

NTSB case
NYC08CA316
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA28-140

Aircraft type
Piper PA28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N2318T
Operator
Holland C. Filgo, Jr · private individual
Onboard fatalities
Unknown
Route
From Nashua Airport / Boire Field (ASH), Nashua, NHTo Sugarloaf Regional Airport (B21), Carrabassett, ME
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

According to the pilot, he completed a left base turn to final for landing on Runway 17. He reduced power, "attempted to flare," and the airplane landed "very" hard. He stated that the airplane "appeared to be porpoising" and bounced hard two more times before it slid to a halt. The pilot reported that there were no mechanical deficiencies with the airplane. He concluded, "My best guess is that my speed was too high and I was trying to land by instinct rather than watching the airspeed." The pilot reported that the winds were from 180 degrees at 4 knots.

Probable cause

The pilot's improper landing flare.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC08CA316
Event ID
20081009X21452
Case number
NYC08CA316
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 91d99592c099a35f9d3c3c18a71a5f3bc14b49861225102d94f170ef60794ef7; retrieved 2026-09-15T10:26:57.296Z.