GAA18CA281 · Piper PA 32R 300
Axiom Capital Solutions Piper PA 32R 300 · Accident: abnormal runway contact during landing
From Burlington Alamance Regional Airport (BUY) to Star Hill Golf Club Airport (60NC)
Event
- NTSB case
- GAA18CA281
- 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 PA 32R 300
- Aircraft type
- Piper PA-32
- 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
- N25WE
- Operator
- Axiom Capital Solutions
- Onboard fatalities
- Unknown
- Route
- From Burlington Alamance Regional Airport (BUY), Burlington, NCTo Star Hill Golf Club Airport (60NC), Cape Carteret, NC
- Aircraft age
- About 37 years (built 1981)
- 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 · landing roll
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot in the retractable-landing gear-equipped airplane, he set up for an extended final approach to the sandy turf runway. He waited until he cleared the trees and "then…dropped down to land." The main landing gear touched down first, followed by the nose landing gear. The main and nose landing gear collapsed upon contact with the runway. The pilot reported that the airplane slid about 300 ft before it came to a stop on the right side of the runway.
The airplane sustained substantial damage to both wings and the lower fuselage.
The Federal Aviation Administration aviation safety inspector who examined the airplane at the accident site reported that witnesses stated that the pilot landed the airplane hard on the sandy turf surface. However, the pilot stated that he did not. However, the pilot did state that he really had to bring the airplane in steep over the trees to get it on the runway.
Photographs provided by the operator showed vertical deformation of both wings at the main landing gear mount location.
Probable cause
The pilot’s steep approach, which resulted in a hard landing and the collapse of the landing gear during touchdown.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA281
- Event ID
- 20180514X30342
- Case number
- GAA18CA281
- 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. 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: 7bfbb47878c7ff3921122014fbf761bebcd4f43859262f8992653283343f2169; retrieved 2026-09-16T07:09:55.474Z.