This N-number isn't registered right now. Below is its last known registration, canceled Mar 5, 2018.
Safety record in brief:1 NTSB accident (substantial damage, Mar 2006)No ADs since 1998 matched1 service difficulty report
We never show street addresses, even though they appear in the public FAA file. Individual owners are shown by city and state only.
Total time and engine hours aren't public. They appear here once the owner adds logbooks.
Individual owners are shown by city and state only.
The operator's inadequate maintenance of the fuel computer harness which resulted in engine surging and a subsequent loss of control by the flight crew during the takeoff roll.
From NTSB records; matched by N-number.Read NTSB report (search CAROL for NYC06LA081)
These match the airframe or engine model. Whether each one applies, and whether it's been complied with, depends on serial numbers, equipment and logbook entries. Applicability must be confirmed by a mechanic against the aircraft's records.
No ADs published since 1998 matched this airframe or engine model.
AI-extracted — verify against original. Matched from each AD's applicability section; ADs replaced by a later AD are left out.
Reports of failures and defects that operators and repair stations sent to the FAA since 1995. A report describes one finding; it is not an accident.
ON DEPARTURE, PILOT HEARD AN UNUSUAL NOISE WHEN GEARS CAME UP. EVERYTHING LOOKED OK. AFTER LANDING, PILOTS NOTICED ON WALK-AROUND ONE OF THE LEFT MAIN TIRES - ALL THE TREAD WAS GONE, SEPARATED FROM THE TIRE. TIRE DID NOT GO FLAT. NEW TIRE, SECOND OCCURRENCE THIS MONTH. LANDINGS: APROX 20. (X)
From FAA Service Difficulty Reports; matched by N-number and serial number.