NYC95LA165 · Cessna 310Q
Cessna 310Q · Accident: hard landing
From Albany International Airport (ALB) to Buffalo Niagara International Airport (BUF)
Event
- NTSB case
- NYC95LA165
- 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
- 0
- 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 310Q
- Aircraft type
- Cessna 310
- 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
- N310JM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albany International Airport (ALB), Albany, NYTo Buffalo Niagara International Airport (BUF)
- 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
- 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, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane initially touched down on runway 32 with approximately 3981 feet remaining. Runway 32 was 5376 feet long and 150 feet wide. The pilot stated that initial contact with the runway was 'a little harder than usual' and the airplane bounced. He added power, and the airplane began to 'float.' When he reduced power, the right wing struck the ground. The investigation revealed that during the landing sequence, the right main landing gear collapsed. The pilot had stated to FAA inspector(s) that during initial touchdown, he was 'glad this flight was over, he was getting tired.' According to the pilot, he had started work at approximately 1400 and had flown to Albany at about 1830.
Probable cause
The pilot misjudged the flare, resulting in a hard landing and subsequent collapse of the right main landing gear. Pilot fatigue was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA165
- Event ID
- 20001207X04066
- Case number
- NYC95LA165
- 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. 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: 64337db4243500a30021b1f1668f338fd6cbe54b0f3dca023496d4857eaf1691; retrieved 2026-09-22T23:35:11.609Z.