N68AM
Registered owner: RFA LLC, MO (owner ≠ operator)
Operators of this aircraft
Who operated this tail, and how firmly we know it.
No operator established for this aircraft.
Accident & incident history
No NTSB accidents or incidents on file for this aircraft.
Maintenance disclosures
Service Difficulty Reports filed with the FAA for this airframe. Filing is largely voluntary — the number of reports is not a measure of reliability. To verify a report, search its control number at the FAA SDRS site.
2 reports on file, 2008-11-01 – 2009-11-14.
Part: COMPUTER — ODOR (PITCH AND ROLL)
PITCH AND ROLL CSAS WENT OFF LINE AND CAME BACK ON LINE. THEN SMELLED BURNING ODOR AND CSAS WENT OFF LINE AND DID NOT COME BACK ON LINE.
Part: COMPUTER — INTERMITTENT (AUTOPILOT SYS)
PILOT REPORT - DURING A FLIGHT TO SAINT FRANCIS HOSPITAL, THE AIRCRAFT BEGAN TO HAVE VERY STRONG UNCOMMANDED YAW INPUTS. THE PILOT DISENGAGED THE YAW CSAS BUT STILL FELT WHAT HE THOUGHT WAS UNCOMMANDED YAW INPUTS. BOTH ENGINES INDICATED NORMAL. THE PILOT THEN MADE A PRECAUTIONARY LANDING AND NOTIFIED MAINTENANCE. MAINTENANCE REPORT - WHEN THE MECHANIC MADE A VISUAL INSPECTION OF THE TAIL ROTOR AND CONTROLS. THE MECHANIC ALSO CLEANED AND REINSTALLED THE YAW CSAS COMPUTER ELECTRICAL CONNECTORS. THE AIRCRAFT WAS THEN FLOWN IN THE LOCAL AREA AND HAD NO PROBLEMS. THE AIRCRAFT WAS RETURNED TO SERVICE AND FLOWN BACK TO THE BASE. APPROXIMATELY TWO HOUR LATER, THE NEXT DUTY PILOT EXPERIENCED THE SAME UNCOMMANDED YAW INPUTS. THE AIRCRAFT WAS GROUNDED AND THE MECHANIC ORDERED A YAW CSAS COMPUTER. THE COMPUTER WAS CHANGED THE NEXT DAY AND THE AIRCRAFT WAS FLOWN AGAIN FOR 15 MINUTES WITH NO YAW ISSUES. THE AIRCRAFT WAS THEN PUT BACK INTO SERVICE AND HAS HAD NO FURTHER ISSUES.