FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC06CA059 · Cessna R182

21 Jan 2006 · Bedford, MA, United States

Civil Air Patrol Cessna R182 · Accident: hard landing

From Westover Metropolitan Airport / Westover Air Reserve Base (CEF) to Laurence G Hanscom Field (BED)

Report a problem

Event

NTSB case
NYC06CA059
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 R182

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
N6278T
Onboard fatalities
Unknown
Route
From Westover Metropolitan Airport / Westover Air Reserve Base (CEF), Chicopee, MATo Laurence G Hanscom Field (BED), Bedford, MA
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 · landing roll
First occurrenceThe 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

  • Pilot in command › Flare, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

After landing on runway 29, the airplane became airborne again during the landing roll. It then started to porpoise and the nose gear contacted the runway hard. The pilot aborted the landing, performed another approach to the runway, and landed without further incident. Post flight inspection of the airplane revealed damage that included firewall buckling in several places. Winds reported at the airport about the time of the accident, were from 240 degrees at 19 knots, gusting to 26 knots.

Probable cause

The pilot's improper flare resulting in a hard landing. A factor in the accident was the wind gusts.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06CA059
Event ID
20060223X00219
Case number
NYC06CA059
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 12123c4b547028ba3b18cd76626f3486a5104f0e17e40ba8cce644ab73837dc3; retrieved 2026-09-22T05:08:51.468Z.