Aircraft that carried N4072T · 2
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N4072T now.
NTSB investigations on N4072T · 3
Of this N-number, whichever aircraft carried it.
NTSB LAX02LA213Accident · Serious injuriesLimited investigationFinal reportRobinson R22 Beta · Chatsworth, CAThe pilot's inadequate flare resulting in rotor blade contact with the ground. Contributing factors were the high altitude and the airframe vibration for an undetermined reason.NTSB LAX00LA079Accident · No injuriesLimited investigationFinal reportRobinson R22B · Piru, CAFailure of the pilot to maintain control after encountering a dynamic rollover.NTSB LAX93LA147Accident · No injuriesLimited investigationFinal reportRobinson R-22 Beta · Folsom, CAThe student pilot's excessive rate of descent during a approach for landing, improper remedial action to arrest the rate of descent, and a failure to maintain proper main rotor RPM. The student pilot's lack of total aeronautical experience was a factor in…
FAA incident reports on N4072T · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20020702013979ARobsin R22BETA · Chatsworth, CA(.19) On July 02, 2002, at 1445 pacific daylight time, a Robinson R22 beta helicopter, N4072T, was substantially damaged following a loss of control during a precautionary landing near Chatsworth, California. The private pilot sustained minor injuries and his…Accident 20000122008879ARobsin R22BETA · Piru, CA(-23) Following a landing in the sandy river bottom in the Piru practice area (santa clara river near Piru, CA) and during the ensuing lift-off, the pilot, concerned about a low flying fixed wing in the aea, was planning a 90 degree right pedal turn to check…Accident 19930311004959ARobsin R22BETA · Folsom, CAHigh steep approach flared. Rotor RPM decayed. Landed hard bounced into air. Rolled over on second touchdown.