GAA15CA142 · Cessna 182P
Cote Orphan Cessna 182P · Accident: hard landing
From Carroll County Regional Jack B Poage Field (DMW) to Carroll County Regional Jack B Poage Field (DMW)
Event
- NTSB case
- GAA15CA142
- 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
Cessna 182P
- Aircraft type
- Cessna 182
- 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
- N1248S
- Operator
- Cote Orphan
- Onboard fatalities
- Unknown
- Route
- From Carroll County Regional Jack B Poage Field (DMW), Westminster, MDTo Carroll County Regional Jack B Poage Field (DMW), Westminster, MD
- Aircraft age
- About 39 years (built 1976)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor and student pilot were conducting practice takeoffs and landings while remaining in the airport traffic pattern. During the third landing, with the student pilot at the flight controls, the nose wheel impacted the runway and the airplane porpoised. The flight instructor assumed control of the airplane, landed, and taxied off of the runway. After clearing the runway, the accident airplane received a transmission over the airport's common traffic advisory frequency that the propeller had impacted the runway during the porpoise.
The flight instructor stated there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. Postaccident examination of the airplane revealed substantial damage to the fuselage and engine firewall.
Probable cause
The flight instructor's delayed remedial action during the landing flare, which resulted in a hard landing and porpoise.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA142
- Event ID
- 20150629X01239
- Case number
- GAA15CA142
- 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: c0917e40110d61b9de18ceaa7f0b383a4f0cffc165f88d3c26318843d50cf27a; retrieved 2026-09-16T02:27:45.245Z.