Avionics Editing and Proofreading Services
An autopilot may disconnect itself twice a month, always in cruise and never while a technician is observing. Each time, the shop runs its standard tests, finds nothing, records "no fault found, system tested satisfactory, returned to service" and reinstalls the same unit. After six months and four such reports, no one may have asked whether the fault appears only above a certain altitude, at a certain temperature or after a certain number of hours since the last power cycle, and no report has recorded the conditions under which the fault failed to appear, only that it did not appear during the test.
The documents we edit for Avionics
"No fault found" and troubleshooting reports are the documents we receive most often from repair stations, together with return-to-service statements and release documentation and reports of interference and intermittent faults. We also receive records of software and configuration changes, documentation of bench and ground tests, and correspondence with operators about recurring, unresolved faults. Our editors work on the report written after a fault that cannot be reproduced on demand.
What the editing involves
The conditions of the test are what turn a "no fault found" report into evidence rather than a closed file, and the characteristic failure is a report that records what was done without recording what it could not reproduce. "Tested satisfactory" states that the unit functioned on the bench; it does not state whether the bench resembled the conditions that produced the fault. The conditions of the original occurrence belong in the report precisely, taken from the pilot report: altitude, phase of flight, outside air temperature and elapsed time since power-up.
Those conditions must then be compared with what the bench could actually reproduce, because a ground run at 70 degrees cannot exclude a fault that appears at cruise altitude after two hours of flight. Every previous occurrence of the same fault on the same unit also belongs in the report, since four "no fault found" reports on one component indicate a pattern of intermittent behavior rather than four unrelated events. What was checked should be itemized rather than summarized as "system tested", because a reader six months later needs to know whether the wiring, connectors and software configuration were examined or only the unit itself.
"Fault not present during test" and "fault does not exist" are different claims, and only the first is supported by a ground run. Where a fault cannot be reproduced on the ground, the report should state this plainly rather than allow the limitation to disappear into a satisfactory result. A recommendation for what would detect an intermittent fault, whether a flight test, a data logger or a period of extended monitoring, belongs at the end. Reports written in this way eventually locate the fault rather than returning the same unit to service four more times.
Confidentiality and the limits of our role
All material sent to us is treated in confidence, including fault histories, technical data and correspondence with operators or manufacturers. We are editors, not licensed avionics technicians or engineers, and we offer no opinion on fault diagnosis or airworthiness. Our role is to ensure that each report states exactly what was and was not established.
Key Avionics vocabulary
- Test performed without conditions recorded
- Tested satisfactory as a claim
- Says nothing about resemblance to the fault
- Conditions of the original fault
- Altitude phase of flight temperature
- Elapsed time since power-up
- Ground test at ambient temperature
- Cannot rule out a cruise-altitude fault
- Prior occurrences referenced
- Pattern of intermittent behavior
- Four unrelated non-events
- What was actually checked itemized
- System tested as a summary
- Wiring connectors and configuration
- Only the unit itself checked
- Fault not present versus fault does not exist
- Different claims same wording
- Only one claim supported by a ground test
- Limitation of the test stated plainly
- Absorbed into a satisfactory result
- Recommendation for what would catch it
- Flight test as a next step
- Data logger monitoring
- Extended monitoring period
- Reinstalling the same unit again
- No fault found report
- Return-to-service statement
- Intermittent fault write-up
- Software configuration change record
- Bench test documentation
- Recurring unresolved fault
Avionics Terminology Check
A short test of specialist terminology. Select the correct answer.
« More Aerospace, Defense and Space editing | All editing services