ERA23FA357 · Robinson Helicopter R22 BETA
N112VG Robinson Helicopter R22 BETA · Accident: loss of control in flight while maneuvering
From Princeton Airport (39N) to an unrecorded destination
Event
- NTSB case
- ERA23FA357
- 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
- 1 · 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
Robinson Helicopter R22 BETA
- Aircraft type
- Robinson R22
- Category
- Helicopter
- 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
- N2356M
- Operator
- N112VG
- Onboard fatalities
- Unknown
- Route
- From Princeton Airport (39N), Princeton, NJTo not recorded
- Aircraft age
- About 30 years (built 1993)
- 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
- Maneuvering
- 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
- Loss of control in flight
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was receiving flight training in the helicopter to upgrade his certificate level, and the accident flight was his second solo flight in the helicopter. The pilot’s flight instructor described that the purpose of the flight was to practice approaches to landing in the airport traffic pattern, but for reasons unknown, the pilot departed the airport traffic pattern, climbed to 1,200 above the ground and flew for about 1/2 mile before making a 180° turn. The helicopter continued for several miles before turning towards a nearby river. An eyewitness who was located on the dam of the river was photographing wildlife with a telephoto lens and observed the helicopter flying erratically towards her. Seeing this, captured photographs of the helicopter and accident sequence. As the helicopter approached, it was in a nose-down attitude, then leveled off. Shortly thereafter, the helicopter began a series of counterclockwise rotations and a series of aggressive pitch and roll changes before the main rotor blades contacted the tail boom. The tail rotor assembly was severed and the helicopter subsequently descended and impacted trees, terrain, and water. The tail rotor assembly was not located after exhaustive searches by multiple parties. The witness photos showed the pilot was bent forward at the waist to the point where his head was touching the helicopter’s windscreen. His arms were visible in several photos, but it is unknown if he was manipulating the controls. He remained leaning forward leading up to and after the loss of the tail boom. His hands and feet, and any associated control inputs to the cyclic, collective, or rudder were not observed. Postaccident examination of the engine, airframe, and systems did not reveal evidence of any preimpact mechanical malfunction or failure that would have precluded normal operation of the engine or airframe. However, with the loss of the tail rotor assembly, a mechanical failure of that system could not be ruled out. In addition, nothing was found indicating a mechanical or foreign object jam of the anti-torque pedals. Toxicological testing yielded negative findings but an autopsy was not performed. Although it is reasonable to consider that an incapacitating medical event might have occurred based on the photographic evidence, such an event is neither supported nor excluded by limited available medical evidence. With the lack of available evidence to support a mechanical failure combined with the lack of medical evidence supporting pilot incapacitation, the cause of the erratic maneuvering leading up to the main rotor blade contact with the tail boom could not be determined.
Probable cause
A loss of control, which resulted in the main rotor blade severing the tail boom, for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA357
- Event ID
- 20230831192977
- Case number
- ERA23FA357
- 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, coordinates, cause areas. 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: 490784067dca136017faf0cb9a5a7e8b77ad32993e75681263d3d3858c3c00f0; retrieved 2026-09-15T08:05:23.295Z.