Table of Contents
1:IntroductionandTaskGroupGeneralFindings
1.1HistoryoftheTG-116TaskGroup
1.2OrganizationoftheTaskGroupReport
1.3TaskGroupOrganizationandActivities
1.3.1TaskGroupOrganization
1.3.2TaskGroupInvestigativeMethods
1.3.2.1ThePrioritizationofFlightSquawks
1.3.2.2TheUseofAirlineMaintenanceDatabases
1.3.2.3TheSymptom/FixMatrix
1.3.2.4DataonRemovedProximitySensors
1.3.2.5TaskGroupParticipationbyOtherVendors
1.4TaskGroupConclusions
1.5TaskGroupLessonsLearned
1.5.1MostNFFproblemsaresystemproblems
1.5.2BITsystemsneedmoreawarenessofsystem
interactions
1.5.3Systemproblemsneedateamsolution
1.5.4Theimportanceofclearandaccuratetechnical
documentation
1.5.5PotentialproblemsintheuseofATAcodes
1.5.6SolutionstomanyNFFproblemsarealready
known,butnotimplemented
1.6Conclusion
1.7MembersoftheTG-116TaskGroup
1.8Appendix1:DescriptionofProximitySensorsandProximity
Systems
1.8.1TheProximitySwitchSystem
1.8.2TheProximitySensor
1.8.3ProximitySensorFailureModes
1.8.4TroubleshootingProximitySensorProblems
1.8.5ImprovedSensorTroubleshootingTool
1.9Appendix2:MD-80PSEUSymptom/FixMatrixforJan.'90-
Sept.'90
2:TechnicalFindings,CorrectiveActionand
Recommendations
2.1StallIndicationFailure
2.2SlatDisagree
2.3AutoslatFail
2.4Autospoiler"DoNotUse"
2.5SpoilerDeployed
2.6RudderTravelUnrestricted
2.7MainGearUnsafe
2.8NoseGearUnsafe
2.9GearDoorOpen
2.10DoorWarning(exceptCargoDoor)
2.11CargoDoorWarning
2.12LandingGearAuralWarning Abstract
Defines the report of the Avionics Maintenance Conference (AMC) Task Group 116 which was formed to discover the causes of "No Fault Found" in avionics equipment during test.