1/3 Flight Test Of Direct Drive Fly-y-wire Flight H W Unclassified Nl .

1y ago
2 Views
1 Downloads
4.07 MB
111 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Audrey Hope
Transcription

AD-All7 24'4 DYNAMIC CONTROLS INC DAYTON OHUNCLASSIFIEDF/6 1/3FLIGHT TEST OF A G. E. AND DCI DIRECT DRIVE FLY-Y-WIRE FLIGHT -ETC(U)F33615-78-C-36096 D JENNEY. H W SCHREADLEYJUN mmmmmmmmmmm

AFWAL-Tlt-82-3035FLIGHT TEST OF A G. E. AND DCI DIRECT DRIVEFLY-BY-WIRE FLIGHT CONTROL SYSTEMGavin D. JenneyHarry W. SchreadleyNCarl N. AllbrightDTr .,kELECTEJUL22 1982DYNAMIC CONTROLS, INC.DAYTON, OHIO 45424FJune 1982 LCDFinal Report for Period October 1978-April 1981-.JApproved for public release;Sdistribution unlimited.FLIGHT DYNAMICS LABORATORYAIR FORCE WRIGHT AERONAUTICAL LABORATORIESAIR FORCE SYSTEMS COMMANDWRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-82 0i 22 .4Wh1 .r/050U

NOTICEWhen Government drawings, specifications, or other data are used for anypurpose other than in connection with a definitely related Government procurement operation, the United States Government thereby incurs no responsibility nor any obligation whatsoever; and the fact that the Government mayhave formulated, furnished, or in any way supplied the said drawings, specifications, or other data, is not to be regarded by implication or otherwise as inany manner licensing the holder or any other person or corporation, or conveying any rights or permission to manufacture use, or sell any patented invention that may in any way be related thereto.This report has been reviewed by the Office of Public Affairs (ASD/PA) andis releasable to the National Technical Information Service (NTIS).At NTIS,it will be available to the general public, including foreign nations.Thistechnical report has been reviewed and is approved for publication./CREC&Y6ICEREProgram ManagerEVARD H. FLINN, ChiefControl Systems Development BranchFlight Control DivisionFOR THE COMMANDERERNEST F. MOORE, Col, USAFChief, Flight Control DivisionFlight Dynamics Laboratory"If your address has changed, if you wish to be removed from our mailing list,or if the addressee is no longer employed by your organization please notifyAFWAL/FIGL, W-PAFB, OH 45433 to help us maintain a current mailing list".Copies of this report should not be returned unless return is required by se-curity considerations, contractural obligations, or notice on a specific docmant.

UNCLASSIFIEDOF THIS PAGE (Won Deta Entered)SECURITY CLASSIriCATIONREAD INSTRUCTIO4S'REPORT DOCUMENTATION PAGE21. REPORT NUMBERGOVT ACCESSION NO.RECIP;ENT'S CA'ALOG NUMBERIN/AN/A /AFWAL-TR-82-30354. TITLE (ndBEFORE COMPLETING FORMTYPE OFSubtitle)SYSTE4TCONTROLFLY-BY-WIRE FLIGHT F7.6.G PERFORMIN ORG. REP DRT NUMBERCONTRACT OR GRANT NUMBER(.Ia.AUTHOR(s)Gavin D. JenneyHarry W. SchreadleyCarl N. Allbright9F33615-7V-C-3609PROGRAM ELEMENT. PROJFCTAREA & WORK UNIT NLIMBERSi0.PERFORMING ORGANIZATION NAME AND ADDRESSDynamic Controls, Inc.7060 Cliffwood PlaceDayton, Ohio 45424II.COj.TROLLING OFFICEAGENCYREPORT DATE-12.iAME AND ADDRESS1982June13. NUMBER OF PAGES107AirWright-Patterson Air Force Base, Ohio 45433MONITORINGTASKProject No. 198?Flight Dynamics UaboratoryLaboratoriesAir korce Wright AeronauticalForce Systemos Command14.REPORT & PERIOD COVEREDFinal- April 19811978OctoberFLIGHT TEST OF A G. E. ANT) DCI DIRECT DRIVENAME & ADDRESS(if different fronrtControlling OfficelSECURITY CLASS. (f15,tD,.sr'oor,Unclassified15a. TATEMENT(of this Report)Approved for Public stribution unlimited(of the abstract entered in Block 20, if different from Report)NOTESNoneI9KEY WORDS (Continue on reverse side iI aecessary and identify by block number)Fly-By-WireFlight ControlsDirect Drive Control ValveDirect Drive ActuationABSTRACT(Continue on reverseaide If necessary and Identify hv block number)This report describes the flight test of twotems which use direct drive control valves.and the test systems are used to control thecraft. One test system was developed by theFly-By-Wire flight control sysThe test aircraft is an F-4Eleft aileron of the test airGeneral Electric Company andthe other by Dynamic Controls, Inc.The report describes the test systems, the aircraft installation, flighttest and results.FORMDD IJN71473EoTON oII\ NOV 651 oesOLETEUNCLASSIFIEDSECURITY CLASSIFICATION OF THIS PAGE (When Data Entered

FOREWORDThe effort described in this document was performed by Dynamic Controls,IInc. of Dayton, Ohio under Air Force Contract F33615-78-C-3609. Thecontract was performed under Project Number 1987, entitled "Flight TestDemonstration of Direct Drive Control Valve for Fly-By-Wire Flight ConWork under the contract was carried out in the Air Forcetrol Systems".Flight Dynamics Laboratory, Wright-Patterson Air Force Base, Ohio andat Edwards Air Force Base, California using Government facilities.The work was administered by Mr. Thomas Lewis and Mr. Gregory Cecere,AFWAL/FIGL Project Engineers.This report covers work performed between October 1978 and April 1981.The technical report was submitted by the authors in March 1982.The authors express their appreciation to Dynamic Controls, Inc. analyst,Heinrich J. Wieg for his contribution in the areas of design.The authorsalso express their appreciation to the program test pilot Captain DanielNims and flight test engineer Captain David Hatfield for their contributions to the program.Accession'ForNTIS GRA&IDTIC TAM-UlannouacedJ12AVB lbllt!CodesAvil nd/orLD.tSpecialiipamimnoz w na

TABLE OF ground21.3Program Summary3DIRECT DRIVE SYSTEMS DESCRIPTION6General6SECTION ISECTION II2.1SECTION IIIDESCRIPTION OF THE TEST SYSTEM AIRCRAFT INTERFACE163.1General Approach163.2G. E. System Interface Hardware173.3DCI System Interface Hardware213.4Interface Hardware Flight Worthiness Testing213.5Mass Change to the Test Aircraft with the Test System243.6The Power Interface-Hydraulic and Electrical26TEST SYSTEM INSTALLATION274.1General274.2G. E. System Aircraft Installation284.3G. E. System Ground Check-Out284.4DCI System Aircraft Installation374.5DCI System41SECTION IVGround Check-OutFLIGHT TESTING465.1General465.2Aircraft Instrumentation475.3Flight Safety Testing52SECTION V5.3.1General525.3.2Aircraft System Stability525.3.2.1G. E. DDCV Stability Considerations525.3.2.2DCI DDCV Stability Considerations535.3.3Ground Check Testing54vPk ODIPA M-NOT fSKM

TABLE OF CONTENTS (Concluded)SECTIONPAGE5.3.4Electromagnetic Interference Testing575.3.5Flight lest Check-Out Testing585.4G. E. System Test Results595.4.1Ground Test Results595.4.2Flight Test Results635.4.2.1Test Flight No. 1635.4.2.2Test Flight No. 2645.4.2.3Test Flight No. 3645.4.2.4Test Flight No. 4675.4.2.5Test Flight No. 4 Two Channel Failure Analysis675.4.35.5Flight Test Results - G. E. DDCV SystemDCI System Test Results69695.5.1Ground Testing695.5.2Flight Test Results - DCI System745.5.2.1Test Flight No. 1745.5.2.2Test Flight No. 2755.5.2.3Test Flight No. 3755.5.3DCI Flight Test Data Analysis78RESULTS SUMMARY AND CONCLUSIONS866.1Geneial866.2Lessons Learned866.3Conclusions and Recommendations87APPENDIX IEMI TESTING89APPENDIX IILATERAL RESPONSE EVALUATION PROCEDURES, WITH TESTSECTION VIAILERON FAILED96REFERENCES98vi

LIST OF ILLUSTRATIONSPAGEFigure1F-4E Test G. E. DDCV FBW System--------------------------------------73G. E. Direct Drive Flight Test Actuator -------------------94G. E. Control Electronics --------------------------------- 105Dynamic Controls, Inc. Direct Drive Control System--------126DCI Control Electronics -----------------------------------147DCI Direct Drive Flight Test Actuator ---------------------158General Test System Installation--------------------------189G. E. System Command Transducer ---------------------------1910G. E. System Control System Monitor-----------------------2011DCI System Command Transducer -----------------------------2212DCI System Interface Power Supply-------------------------2313G. E. Actuator/Input Transducer---------------------------2914G. E. Actuator Installation -------------------------------3015G. E. Electronic Mounting Configuration-------------------3116G. E. Flight Computer Installation------------------------3217G. E. Control System Monitor Installation -----------------3318G. E. Control Electronics Schematic-----------------------3519DCI Actuator CI Input Transducer Installation-------------------------3921DCI Electronics Installation------------------------------ 4022DCI Pilot Monitor Installation---------------------------- 4223aDCI Control System Schematic ------------------------------- 4323bDCI Control System Schematic ------------------------------ 4424Flight Data Recorder Installation-------------------------25System Frequency Response --------------------------------- 5126Pilot's Preflight Checklist G. E. System------------------5527Pilot's Preflight Checklist DCI System--------------------5628Right Aileron vs Lateral Stick ----------------------------6029LVDT vs Lateral Stick------------------------------------- 6130L. H. Aileron vs Lateral Stick ----------------------------- 62vii50

LIST OF ILLUSTRATIONS (Concluded)PAGEFigure 31G. E. 2 Channel Velocity Time-History --------------------6532G. E. 1 Channel Velocity Time-History--------------------66332 Channel 4Original Power Disconnect ---------------------------------7036Left Aileron vs Lateral Stick-----------------------------7137Input Transducer vs Lateral Stick-------------------------7238Left Aileron vs Input Transducer -------------------------7339P-Q Data for Utility Line from Left Aileron to Reservoir- A/C F4E Nr. t Test Point No. 1-----------------------------------8241Flight Test Point No. 2----------------------------------8342Flight Test Point No. 3----------------------------------- 84viii

LIST OF TABLESTABLE 1COMPONENT WEIGHTS CV SYSTEM PERFORMANCE TESTS -----------------------------483PARAMETER LIST FOR DDCV FLY-BY-WIRE ACTUATOR TEST---------494DCI TEST DATA SMMARY -------------------------------------805TEST CONDITIONS -------------------------------------------97ix

LIST OF ABBREVIATIONSA/CaircraftAFFTCAir Force Flight Test CenterAOAangle of attackBLCboundry layer controlCADCCentral Air Data ComputerCMDcommandDCIDynamic Controls, IncorporatedDDCVDirect Drive Control ValveEAFBEdwards Air Force BaseEMIelectromagnetic interfaceFBYFly-By-WireFCFfunctional check flightG. E.General ElectricIFFindentification systemKIASknots indicated airspeedLEDlight emitting diodesLTleftLVDTlinear variable differential transformerPPilot (front seat)RTrightSASstability augmented systemsSWswitchWPAFBWright-Patterson Air Force BaseWSOWeapons Systems Officer (rear seat)x

SECTION IINTRODUCTION1.1GeneralThis report describes the flight test of two different Direct DriveControl Valve Fly-By-Wire control system mechanizations in an F-4Eaircraft.The Fly-By-Wire control systems were used to control anaileron of the test aircraft.The purpose of the flight test program was to verify satisfactoryperformance of the Direct Drive Fly-By-Wire approach when used toc.ntrol a fighter-bomber aircraft.The flight test hardware evaluated consisted of two systems, one manufactured by the General Electric Company, Binghamton, New York and theother manufactured by Dynamic Controls, Inc., Dayton, Ohio.The sys-tems were tested sequentially.The flight test of the two systems was conducted at Edwards Air ForceBase, California by the Air Force Flight Test Center (AFFTC).I,terfacehardware and flight test support were provided by Dynamic Controls, Inc.This report describes in the following order:(a)The Systems Evaluated.(b)The Test System Interface(c)Aircraft Installations(d)Flight Test of the General Electric System(e)Flight Test of the Dynamic Controls, Inc. System(f)Program Results

1.2BackgroundThe use of electronic primary flight control for aircraft, commonly calledFly-By-Wire (FBW), has brought with it the advantages of precise control andflexibility associated with electronic technology.However, the requirementfor preservation of control with component failures has led to the use ofparallel redundancy levels which are considerably greater than the conventional hydromechanical controls.This is in part due to lack of statisticalconfidence in the components used in a FBW system ksince historical data onFBW flight control systems is not particularly abundant).Present FBW Mech-anizations for primary flight controls use up to four parallel channels ofsignal transmission in addition to three or four electrohydraulic channelsin converting electronic commands to a hydromechanical output.The majorityof the systems developed incorporate redundancy for the electrohydraulics byusing a secondary actuator since the size and power requirements of the poweractuator make incorporating three or four channel redundancy in the poweractuator impractical.Reducing the redundancy level of a FBW system to the two parallel channelsingle-fail-operate level of conventional controls, while meeting aircraftreliability requirements, may be practical with the state-of-the-art technology.If the number of components of the FBW system can be reduced anddeveloped for maximum reliability, the reliability requirement for a singlefail-operate FBW mechanization can be met.The Direct Drive Control Valve (DDCV) accomplishes the simplification of theFBW system for a single fail-operate mechanization.no hydraulic amplification stage is required.For this type of valve,The electromechanical forcegenerator is connected directly to the control spool used to control hydraulic flow to the power actuator.This type of mechanization eliminates thesecondary actuator from the FBW mechanization.This valve concept has been investigated by several companies, specificallyby North American Rockwell (Columbus Division)) General Electric Company(Johnson City), and Dynamic Controls, Incorporated.2The type of force

generator selected for development by each company has been different.North American Rockwell investigated a torque motor configuration.eral Electric developed a linear force motor.Gen-Dynamic Controls, Inc.developed a moving coil force motor.The flight test described in this report is the evaluation of the hardware resulting from Air Force funded direct drive development programs byGeneral Electric and Dynamic Controls, Inc.1.3Program SummaryInstallation and flight test of the two Direct Drive Control ValveDDCV)Fly-By-Wire (FBW) systems occurred during the period from 8 October 1980to 14 April 1981 at Edwards Air Force Base, California.installed in F-4E Aircraft No. 287.The systems wereThe General Electric Companysystem was installed and evaluated first.G. E.)Figure 1 shows the test air-craft during installation of the DDCV systems.Both DDCV FBW systems were used to control the left aileron of the testaircraft.The test hardware was designed to match the original aileron'sperformance characteristics.This was done in order to maintain symetricalcontrol characteristics in roll, since only one aileron was changed to FBWcontrol.The DDCV mechanizations evaluated were similar in concept, but differentin execution.The G. E. mechanization used a linear force motor attachedto the normal aileron actuator's control valve and linear variable differential transformers (LVDT's) for position measurement.trols, Inc.The Dynamic Con-(DCI) mechanization used voice coil force motors attached toeach end of a control valve which replaced the normal aileron controlvalve and housing.Linear potentiometers (direct current) were used inthe DCI mechanization for position measurement.The G. E. mechanizationrequired both 28 volt DC and 115 volt 400 Hz AC electrical power for operation.The DCI system required 28 volt DC power for its operation.3

\-NUU2c-iHC)U4

Interface hardware used in mounting the DDCV electronic assemblies for bothsystems was fabricated by DCI and flightworthiness tested prior to start ofthe installation into the aircraft.was used for both systems.A common wiring harness for controlAdapter cables were used to interface each in-dividual system to the common harness.As originally scheduled with Edwards Air Force Base, the installation andflight test period was to be from June 1979 to June 1980.initially assigned was F-4E aircraft No. 368.The aircraftHowever, prior to start ofinstallation, aircraft 368 became unavailable.The test aircraft was thenchanged to No. 287 and because of the assignment of higher priority programsto the aircraft the length of time for installation and test reduced fromtwelve months to six months.time obtained for each system.This change impacted directly upon the flight(The installation time originally scheduledwas the same as the total installation and flight test time for the new aircraft assignment.)The period from 8 October 1980 to 20 February 1981 wasused for installation and flight test of the G. E. system.The remainingseven weeks to 14 April 1981 were used to install and flight test the DCIsystem.Due to both incidential maintenance requirements on the test air-craft and the length of time required to install and wring-out the testsystems, the flight test time obtained on each test system was less thanthe 25 hours per system originally planned.However, both systems weresuccessfully flight tested over most of the planned test envelope and exhibited performance characteristics similar to the normal aircraft aileroncontrol system.Although the limited flight test time did not indicate longterm reliability characteristics, the program did demonstrate satisfactoryflight performance of the DDCV mechanization for both systems.5A. i.I4

SECTION IIDIRECT DRIVE SYSTEMS DESCRIPTION2.1GeneralThe General Electric Company and the Dynamic Controls, IncorporatedDirect Drive Control Valve FBW mechanizations were designed and developedindependently, under separate Air Force contracts.Both systems arebasically the same in concept, using fail-operate (two channel) redundancywith a single stage servovalve driven by electrical force motors.force motors of both mechanizations have four coilsand four corresponding current drivers.Thetwo per channel)Both mechanizations were de-signed to be applied to the left aileron control of the F-4 aircraft,changing the normal actuator from a mechanical input actuator to FBWcontrol.Both mechanizations are based on modification of the normalF-4 actuator control valve assembly and the addition of electrical feedback position transducers to the normal actuator.The General Electric Company mechanization is described in detail in thetechnical report, AFFDL-TR-78-32.The Dynamic Controls, Inc. mechaniza-tion is described in detail in the technical report AFFDL-TR-77-91.Thefollowing material in this section is a summary description of the twoDDCV mechanizations.2.2General Electric System DescriptionFigure 2 is a block diagram of the General Electric system.The systemis designed using a force motor that has a moving armature and four drivingcoils which are driven by individual servoamplifiers (two coils and twoservoamplifiers per channel).The force motor has two inner loop positionfeedback LVDT's (one per channel) with two independent outputs which areset up out of phase in order to implement a self-monitoring scheme.6

-------I01DVFWSse2Figure G.E7-I

There are two command and two actuator position LVDT's per channel.With-in each channel one set of command and feedback transducers are summed atthe CIM servoamplifier and the other set of transducers are summed at themodel servoamplifier.The error signal developed at each servoamplifierdrives the independent coils of the force motor within the respective control channels.The two channels have a cross strap from Channel 1 failure logic to Channel2 CMD and model servoamplifiers.The cross strap acts as a gain changerallowing Channel 1 to act as a master channel until Channel i fails, (orboth channels have large error signals) then Channel 2 switches to normalsystem gain.Should Channel 2 fail, there is no effect on Channel i out-put,The failure logic monitors the status of each channel's power supply, servoamplifier error voltage, force motor current and force motor position LVDToutput.The failure logic disconnects the servoamplifiers from the forcemotor coils and provides a failure indication when the signals being monitored exceed their disagreement limits.Figure 3 shows the G. E. Direct Drive Flight Test Actuator.The force motoris attached to the manual input control valve normally used on an F-4 aileron actuator.The position transducers measuring the actuator output positionare mounted in the center depression of the actuator body.Figure 4 shows the G. E. control electronics used with the direct drive actuator.2.3A single box contains both the Channel 1 and the Channel 2 electronics.Dynamic Controls, Inc. System DescriptionFigure 5 is a block diagram of the Dynamic Controls, Inc. control system.The control system is a fail-operate configuration (as is the G. E. system)where any single hydraulic or electrical failure does not prevent the control system from operating with a satisfactory level of performance.TheI8,

ca4.J-441Un

vita414#A-40-o0-0100

system uses two self-monitored control channels and a two section electro-hydraulic control actuator.The control actuator uses two force motors con-nected directly to the tandem control spool which meters hydraulic flow tothe actuator drive areas.In normal operating mode, both self-monitoring control channels operate,driving both moving coil force motors.The power spool is spring centered.Either control channel can apply sufficient driving force to the tandemspool to achieve maximum stoke.The two self-monitored control channelsare completely independent (both mechanically and electrically) down tothe tandem power spool.Channel independence is necessary to eliminate thepossibility of a common mode failure of the two control channels.For the system to meet the "fail-operate" criteria, hardover failure of acontrol channel must be prevented.Hardover failures of command and feed-back elements are detected and removed from affecting the channel output byusing two monitor command and feedback elements for each control channel.As shown in Figure 5, command input 2 and feedback 2 are used as the monitor for command input I and feedback 1.The monitor feedback and commandelement outputs are compared with the output of the comand and feedback elements used to control the servoamplifiers connected to the force motor.Thecomparison is made after the summing junction for the command and feedback signals.Disagreement between the command and monitor portions of each controlchannel causes the command portion to be disconnected from control of theservoamplifiers.To prevent hardover channel outputs due to servoamplifierfailure, two servoamplifiers and two force motor coils are used in each channel.The servoamplifiers are cross-strapped in their current feedback pathsso that failure of one amplifier-coil section are offset by the output of theother section.Four independent electrical power supplies and two hydraulicpower supplies must be used to allow the system shown in Figure 5 to acceptsingle electrical or hydraulic failures and continue to operate.Figure 6 shows the electrical components of the DCI system.The electroniccircuits are constructed as modules in order to provide fail-operate capa-11

00-44AIU)3-4144-4-30iC-.)Ln.0H00ulLn1210

bility after a single weapon impact.The size of the control electronicsis primarily determined by this single hit survivability requirement usedfor the hardware design.The system electronics use a total of 16 opera-tional amplifiers for control and failure detection.The modules with cool-ing fins are the servoamplifiers used to control the force motors.as part of the system is a control system monitor module.IncludedThe control systemmonitor module uses an additional 8 operational amplifiers as light driversfor the display lights.Besides in-flight status display, the module al-lows preflight functional checking of each servoamplifier's operation andthe operation of the failure monitor and disconnect circuits.Fiber opticcables are used to transmit status information from the servoamplifiers tothe control system monitor module.The fiber optics are connected betweenlight emitting diodes (LED'S) in the servoamplifiers and light drivers inthe control system monitor module.The LED drivers are designed to illuminatewhen a servoamplifier's output reaches a particular level (for each directionof current flow).Fiber optics are used to prevent failure of the status dis-play lines from affecting the functioning of the control system.Figure 7 shows the DCI Direct Drive Flight Test Actuator.The force motorsare mounted to a control valve body which replaces the normal manual inputcontrol valve.A force motor is used at each end of the control valve.Chan-nel 1 of the control electronics is connected to one force motor and Channel2 is connected to the other.The position potentiometers are mounted in thecenter depression of the actuator body.I113

14

15

SECTION IIIDESCRIPTION OF THE TEST SYSTEM AIRCRAFT INTERFACE3.1 General ApproachThe purpose of installing the DDCV FBW systems in the F-4 aircraft was todemonstrate the feasibility of utilizing that type of control sys-em in anaircraft's primary flight control system. The selection of the aileron axisfor the location of the test systems was made early in the hardware development programs for both systems. The philosophy of using a single aileroncontrol channel is that a hardover failure of a test system could be compensated with the normal aircraft spoilers and the opposite aileron. The "E"model of the F-4 aircraft was recommended by Edwards AFB as the test aircraft because that particular model of the F-4 has controllable slotted leading edges on the wings, allowing a larger angle of attack before loss of control.The direct drive test hardware was designed to match the normal aileronhardware performance. Therefore, the criteria for success of the DDCVFBW systems was that they provide performance with no significant differencefrom that of a normal F-4 aircraft aileron system.Normally, installation of a FBW system as a replacement for a hydromechanicalcontrol system will provide improved control sensitivity by eliminating hysteresis and deadband induced by the mechanical linkages. However, for thetest system (since FBW was applied to only one of the ailerons of the testaircraft) the command transducers for the test systems were mounted at theend of the normal mechanical. linkage chain. This mounting choice was madeto retain the same sensitivity characteristics in both the right and leftroll modes and to allow the surface trim and autopilot mechanization tofunction normally.The two test systems, although functionally similar, were mechanized withsufficient differences that direct interchangeability of individual components was not possible.In designing the Class II modification for the16

test aircraft, a common wiring harness was used.Short adapter cableswere used (where required) to couple specific components of a system tothe harness.This wiring approach minimized the effort required to changefrom one test system to the other.Both systems included a control systemmonitor module, control electronics, a DDCV actuator and a command transducer.craft.Figure 8 shows the location of these components in the test airThe DDCV actuator for both systems replaced the normal aileron ac-tuator in the left wing.The command transducer was mounted adjacent tothe DDCV actuator, at the end of the control linkage chain.This locationfor the command transducer provided the normal trim and automatic flightcontrol system inputs to the left aileron actuator.The control systemelectronics for both systems was installed in the upper equipment bay behind the rear seat.Electrical power connection to the appropriate air-craft supply voltages (115 volts @ 400 Hz and 28 VDC for the G. E. system,28 VDC for the DCI system) was made through relays and circuit breakersmounted in the rear seat cockpit.The control system monitor module wasinstalled in the right-hand console of the rear seat cockpit.3.2G. E. System Interface HardwareTwo components of the test system shown in Figure 8 were fabricated andflightworthinesstested by DCI as part of the flight test interface forthe G. E. system.These components were the command transducer shown inFigure 9 and the control system monitor shown in Figure 10.The G. E.command transducer housed four LVDT's manufactured by Pickering, Inc. tothe same specification used by G. E. for the actuator position transducers.Excitation and demodulation of the command transducers' output was providedin the G. E. electronics package.Figure 9 also shows the mounting bracketand a link used to install the command transducer in the test aircraft.(Only one of the two brackets shown in Figure 9 was used in the aircraftinstallation.)The pilot monitor was constructed to allow preflight test of the G. E.system by the rear seat pilot using the system status indication andchannel reset.As shown in Figure 10, the control system monitor used17

04CA,4C00L)v00-4441 00-1

os)cu19C

U))LLJ 0C-))ZC64002.

three momentary contact switches for each channel to simulate electricalfailure signals in the G. E. control electronics. These failure signalswere used to preflight check the failure detection sections of the controlelectronics.The control system monitor also included a channel resetswitch and a status light for each channel.Failure of a control channelilluminated that particular channel's "off" light.3.3DCI System Interface HardwareThe DCI system required two addi

AIR FORCE WRIGHT AERONAUTICAL LABORATORIES AIR FORCE SYSTEMS COMMAND WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433 82 -0i 22 050 .4Wh1 .- .r/ . 5.5.2.3 Test Flight No. 3 75 5.5.3 DCI Flight Test Data Analysis 78 SECTION VI RESULTS SUMMARY AND CONCLUSIONS 86 6.1 Geneial 86 6.2 Lessons Learned 86

Related Documents:

1.1 why performance flight testing 1.1 1.2 flight test manual objective 1.2 1.3 flight test manual organization 1.3 1.3.1 manual organization 1.3 1.3.2 chapter organization 1.4 1.4 effective test planning 1.5 1.5 responsibilities of test pilot and flight test engineer 1.5 1.5.1 the test pilot 1.5 1.5.2 the flight test engineer 1.7

Flight Operation Quality Assurance (FOQA) programs are today customary among major . EASA European Aviation Safety Agency F/D Flight Director . FAF Final Approach and Fix point FCOM Flight Crew Operating Manual FCTM Flight Crew Training Manual FDAP Flight Data Analysis Program FDM Flight Data Monitoring FLCH Flight Level Change FMC Flight .

Using ASA’s Flight Planner A flight log is an important part in the preparation for a safe flight. The flight log is needed during flight to check your groundspeed and monitor flight progress to ensure you are staying on course. The Flight Planner has two sections; the Preflight side is used for pre-

‘757 Captain’ Sim FLIGHT MANUAL Part III – Normal Procedures DO NOT USE FOR FLIGHT AMPLIFIED PROCEDURES EXTERIOR INSPECTION Prior to each flight, a flight crew member or the maintenance crew must verify the airplane is acceptable for flight. Check: - Flight control surfaces unobstructed and all surfaces clear of ice, snow, or frost.

means before the flight becomes official. A flight of less than 60 seconds duration will be considered a delayed flight; one delayed flight shall be allowed for each of the five official flights. After a delayed flight, the next launch shall result in an official flight being recorde

offically licensed cessna products from saitek pro flight avilable at: www.saitek.com pro flight cessna rudder pedals flight pedals with toe brakes pro flight cessna yoke system flight yoke and 3 lever quadrant modual pro flight cessna trim wheel

GLOSSARY ACMS: Aircraft Condition Monitoring System AFDAU: Auxiliary Flight Data Acquisition Unit APM: Aircraft Performance Monitoring ASR: Aviation Safety Report CRM: Crew Resource Management CVR: Cockpit Voice Recorder DFDR: Digital Flight Data Recorder FDA: Flight Data Analysis FDAU: Flight Data Acquisition Unit FDEP: Flight Data Entry Panel FDM: Flight Data Monitoring

Flight Center will participate in flight training activities to verify safe and effective flight training. 2.2 Chief Flight Instructor The Chief Flight Instructor is responsible for the day-to-day operations of the Flight Center. He is the principle point-of-contact to the FAA for the University of Dubuque. He ensures