Aircraft that carried N66076 · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N66076 now.
NTSB investigations on N66076 · 4
Of this N-number, whichever aircraft carried it.
NTSB DEN02LA033Accident · Serious injuriesLimited investigationFinal reportCessna 172Q · Fruitland, UTthe pilot's failure to apply carburetor heat. Contributing factors included carburetor icing conditions, the unavailability of suitable terrain on which to make a forced landing, and night conditions.NTSB DEN01LA120Accident · No injuriesLimited investigationFinal reportCessna 172Q · Englewood, COthe pilot's failure to properly recover from a bounced landing. A contributing factor were the adverse wind conditions.NTSB DEN92LA043Accident · No injuriesLimited investigationFinal reportCessna 172Q · Englewood, COUndetermined.NTSB DEN88LA211Accident · No injuriesLimited investigationFinal reportCessna 172Q · Broomfield, CO
FAA incident reports on N66076 · 4
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20020315003939ACessna 172Q · Fruitland, UT(-23) During flight from roosevelt, UT to heber, UT at dusk the aircraft lost power. In descent the aircraft encountered severe turbulene and possible stall spin. The pilot recovered into glide and made forced landing in snow covered meadow. Aircraft left…Accident 20010703020729ACessna 172Q · Denver, CO(-23) The student pilot stated that she was returning from a solo cross country trip and was cleared to land on runway 351 at apa. After touchdown, the aircraft began porpoising. The pilot stated she was unable to recover. The aircraft sustained substantial…Accident 19920318009139ACessna 172Q · Denver, COOn preflight noted wing damage from a prior flight. Unable to determine responsible party.Accident 19880918046889ACessna 172Q · Denver, COTaxiing toward tiedown area wind gusts blew aircraft over, NTSB determined this was an incident not an accident.