FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA050 · Piper PA 28-150

9 Nov 2013 · Concordia, KS, United States

Piper PA 28-150 · Accident: hard landing

From Blosser Municipal Airport (CNK) to Blosser Municipal Airport (CNK)

Report a problem

Event

NTSB case
CEN14LA050
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 28-150

Aircraft type
Piper PA-28
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
N5790W
Onboard fatalities
Unknown
Route
From Blosser Municipal Airport (CNK), Concordia, KSTo Blosser Municipal Airport (CNK), Concordia, KS
Aircraft age
About 49 years (built 1964)
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
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor and student pilot reported that they used soft-field procedures for takeoff. After lifting off with a high-pitch attitude, the pilots continued to climb the airplane using a high-pitch attitude to clear a simulated obstacle. With a partial flap setting, tailwind condition, and high-pitch attitude, the airplane struggled to climb and approached a stall. The flight instructor chose to make an off-field landing, which resulted in substantial damage to the left wing. Postaccident examinations of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

The flight instructor’s improper decision to attempt a climb with an excessive pitch attitude for the tailwind condition and flap setting, which resulted in an approach to stall and subsequent off-field landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA050
Event ID
20131112X93534
Case number
CEN14LA050
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: ff3e5d635716da5dffc5156f3e472683f5c0c9701bf5713620f5e5b86e3f8463; retrieved 2026-09-15T23:06:03.362Z.