FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA15CA069 · Buhlmann Howard HB-1

8 May 2015 · Canandaigua, NY, United States

Buhlmann Howard HB-1 · Accident: landing area undershoot

From Canandaigua Airport (D38) to Canandaigua Airport (D38)

Report a problem

Event

NTSB case
GAA15CA069
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

Buhlmann Howard HB-1

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
N170HB
Onboard fatalities
Unknown
Route
From Canandaigua Airport (D38), Canandaigua, NYTo Canandaigua Airport (D38), Canandaigua, NY
Aircraft age
About 6 years (built 2009)
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
Landing area undershoot
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
  • Personnel issues › Task performance

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

NTSB narrative

Due to the crosswind component, the pilot chose to land on an unpublished grass runway on the airport. According to the pilot, he approached the landing area low and slow without sufficient power to clear a culvert prior to the intended touchdown zone. The right landing gear impacted the culvert and the airplane departed the left side of the runway. The airplane came to rest after impacting a ditch to the left of the grass runway.

The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The airplane sustained substantial damage to the right side of the fuselage.

Probable cause

The pilot's failure to land beyond the marked runway threshold, which resulted in a collision with a culvert and a loss of control on the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA15CA069
Event ID
20150514X31030
Case number
GAA15CA069
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: b8000463f19227994db87955955dcf2763bf76d323938c4862f8e761f6dcb482; retrieved 2026-09-16T02:18:50.129Z.