This N-number isn't registered right now. Below is its last known registration, canceled Feb 22, 2001.
Safety record in brief:1 NTSB accident (substantial damage, Sep 2000)1 AD may apply
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 pilot did not properly flare the airplane during the aborted takeoff and he failed to maintain directional control of the airplane during the landing roll. Factors associated with the accident were the partial power loss for undetermined reasons and the trees that the airplane contacted.
From NTSB records; matched by serial number.Read NTSB report (search CAROL for CHI00LA294)
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.
| AD | Subject | Effective | Applies to |
|---|---|---|---|
| 99-05-13 | Raytheon Aircraft Company 17, 18, 19, 23, 24, 33, 35, 36/A36, A36TC/B36TC, 45, 50, 55… | Apr 19, 1999 | Airframe (B24R)Certain serial numbers: F33A CE-290–CE-1791; E33C CJ-26–CJ-179; F33C CJ-26–CJ-179; A36 E-185–E-3046; B36TC EA-242–EA-591; 58 TH-1–TH-1798 |
AI-extracted — verify against original. Matched from each AD's applicability section; ADs replaced by a later AD are left out.
No Service Difficulty Reports found for this airframe since 1995.