ERA10CA273 · Cirrus Design Corp SR22
3D Group Cirrus Design Corp SR22 · Accident: dragged wing/rotor/float/other on approach
From Greater Binghamton/Edwin A Link field (BGM) to Republic Airport (FRG)
Event
- NTSB case
- ERA10CA273
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N960JB
- Operator
- 3D Group
- Onboard fatalities
- Unknown
- Route
- From Greater Binghamton/Edwin A Link field (BGM), Binghamton, NYTo Republic Airport (FRG), Farmingdale, NY
- 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
- Approach · VFR go-around
- 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
- Dragged wing/rotor/float/other
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot/owner, he decided to "go around" at the completion of a practice instrument approach. After the application of full engine power, "the P-factor, along with the cross-wind from the right, caused my left wing and left main landing gear to hit the ground momentarily." The pilot then reduced power to keep the airplane on the ground. The airplane departed the left side of the runway and struck a sign and an embankment, which resulted in substantial damage to the wings and the airframe. Following the accident, the pilot reported to a Federal Aviation Administration inspector that there were no deficiencies with the performance and handling of his airplane.
Probable cause
The pilot's failure to maintain directional control during a go-around attempt.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA273
- Event ID
- 20100520X60222
- Case number
- ERA10CA273
- 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: dfa4b96178473f6ddd8f713820d0429aa32b5d6e90e3d11df81c7481dc1486bc; retrieved 2026-09-15T14:09:14.906Z.