Third European Flight Test Safety Conference Vienna Austria

  • Slides: 31
Download presentation
Third European Flight Test Safety Conference Vienna, Austria November 11 – 12, 2009 Boeing

Third European Flight Test Safety Conference Vienna, Austria November 11 – 12, 2009 Boeing 777 First Flight And the Days Before John Cashman Boeing Commercial Airplanes (Retired) W 029 f.

First Takeoff June 12, 1994 2

First Takeoff June 12, 1994 2

First Takeoff June 12, 1994 3

First Takeoff June 12, 1994 3

Philosophizing • “One test flight is worth a thousand theories” – Tex Johnston –

Philosophizing • “One test flight is worth a thousand theories” – Tex Johnston – Boeing Airplane Company ~ 1952 – First flights – B 52, 707 – This simple statement is as true today, 57 years later, as – it was in Tex’s day. • First flights present ample possibilities to test a – number of theories and generally provide – opportunities for all concerned to excel. • Modern jet transports, even those developed with – sophisticated technical tools, still need a disciplined – first flight ground and flight test plan to minimize risk – to the program and crew. 4

First Flight Goal Setting First flight goals are not just technical – they may

First Flight Goal Setting First flight goals are not just technical – they may have elements of financial, political, schedule, or public relations goals intermixed • The Basics • Have a safe flight • Demonstrate readiness of airframe and engine to start the test program • Provide a positive media event • To get the team focused on the remainder of the test program, not just one flight 5

First Flight Goal Setting - cont’d Additional 777 Goals • Demonstrate to our customers

First Flight Goal Setting - cont’d Additional 777 Goals • Demonstrate to our customers that the airplane is ready to test and that the aggressive schedule is achievable and will result in an on time delivery • Demonstrate to the certification authorities that the airplane program is “mature” and has the potential to receive over water approval from the time of initial certification rather than after 250, 000 engine hours in fleet service • Demonstrate confidence to the public as well as organizations representing airline labor and the public press 6

Insuring Success – First Flight and Beyond • Why the worry? • Previous experience

Insuring Success – First Flight and Beyond • Why the worry? • Previous experience with our 747 -400 in the late 1980’s pointed out that large scale integrated digital system design and flight testing required more preparation, planning, and full up system testing than earlier mechanical or analog systems. Not anticipating these factors had: • slid schedule – flight test, delivery, crew training • cost money – us and our customers • given our customers not quite service ready products (airplane, support products, additional training) 7

Insuring Success – First Flight and Beyond • Led certification authorities to question our

Insuring Success – First Flight and Beyond • Led certification authorities to question our design and manufacturing test processes and to add many hours of additional testing • * “Normal” flight testing of the 747 -400 had failed to find many problems that occurred in daily“real world” airline operations • commercial aircraft power cart variability • power interrupts • maintenance manual errors and outdated training for fixing faults 8

Elements of the Plan • 1) Co-located Integration Lab (500, 000 sq. ft) which

Elements of the Plan • 1) Co-located Integration Lab (500, 000 sq. ft) which included • A) Fixed base simulators (2) • Flight deck engineering development • Flight control law definition • Initial cadre training of FAA, customer pilots, prior to full flight training simulator • Flight test engineering sequence tests, including engineering run through of first flight and first two months of testing 9

Elements of the Plan – cont’d A) Simulators – cont’ * Checkout of changes

Elements of the Plan – cont’d A) Simulators – cont’ * Checkout of changes to flight controls airplane information management systems (devices used for real aircraft parts) * First up 3 years before first flight 10

Remember, pull back - houses get smaller, push forward - houses get bigger. 11

Remember, pull back - houses get smaller, push forward - houses get bigger. 11

Elements of the Plan – cont’d • B) System Integration Laboratory » Cockpit with

Elements of the Plan – cont’d • B) System Integration Laboratory » Cockpit with simulated aero data » Systems using real production » hardware » Ships generators and wiring » Digital bus simulated outside » parameters to real boxes 12

Elements of the Plan – cont’d B) System Integration Laboratory – cont’ • •

Elements of the Plan – cont’d B) System Integration Laboratory – cont’ • • Included flight test wiring bundles and data systems Full test plans, DR&O validation, “what if” scenarios Supported by design engineering, flight test pilots and engineers, FAA and other certification agencies 13

Elements of the Plan – cont’d • B) System Integration Laboratory – cont’ •

Elements of the Plan – cont’d • B) System Integration Laboratory – cont’ • “Discoveries” written and tracked as flight squawks (before first flight) • Used as a shadow for first flight - program test pilot, flying profile and concurrent with first flight, available by radio • 24 hours/day, 7 days a week, 3 -4 pilots/day for six months leading up to first flight (2493 hours out of 4477 hours total using 34 different pilots) • Key element for solving problems early and avoiding surprises 14

Elements of the Plan – cont’d C) Flight Control Test Rig (Iron Bird) •

Elements of the Plan – cont’d C) Flight Control Test Rig (Iron Bird) • ½ of the primary flight controls, hydraulics, • • computers wiring, flight test instrumentation Simulator cab for control input System familiarization – flight test and engineering as well as Instrumentation checkout Flight test procedure used “Flight” squawks written and tracked – also reviewed by FAA for program status. (Total flight and engineering items 7400 before first flight) 15

Elements of the Plan – cont’d 2) Fly-By-Wire Test Bed • Modified 757 aircraft

Elements of the Plan – cont’d 2) Fly-By-Wire Test Bed • Modified 757 aircraft • F/O controls FBW • Disconnected from aircraft mechanics • Worked through autopilot flight control computers when engaged (some single channel and some dual) • Critical to basic control law validation of C*U control law (ie; blend of Θ and Nz command speed off reference) • 16

Elements of the Plan – cont’d 2) Fly-By-Wire Test Bed » New feature validation

Elements of the Plan – cont’d 2) Fly-By-Wire Test Bed » New feature validation for engine out control, ground effects, turn and configuration compensation » Demonstrated concepts to company management, customers, certification authorities, and pilot organizations, as well as a variety of our own internal pilot cords. » Flew 250 hours, 1 – 1½ years before first flight 17

757 Test Bed 18

757 Test Bed 18

Elements of the Plan – cont’d 3) Flying Engine Test Bed • #1 747

Elements of the Plan – cont’d 3) Flying Engine Test Bed • #1 747 -100 airframe for 2 engine companies • #16 747 -100 used by other • Initially resisted by two of the three engine • companies • Boeing Propulsion staff due to • belief that ground testing is adequate 19

Elements of the Plan – cont’d 3) Flying Engine Test Bed • • •

Elements of the Plan – cont’d 3) Flying Engine Test Bed • • • FTB was insurance policy for program Schedule, certification, and public relations Plan on early over water approval Many “discoveries” were made that, in fact, would have had significant impact on engine operability and restart capability • Initial testing done 7 months before first flight • for first engine 20

747 Engine Test Bed 21

747 Engine Test Bed 21

747 Engine Test Bed 22

747 Engine Test Bed 22

Elements of the Plan – cont’d • 4) Flight Emulation Test System (FETS Van)

Elements of the Plan – cont’d • 4) Flight Emulation Test System (FETS Van) • Ground base simulation of flight data and • airplane aero data • Can “fly” the airplane with all systems running as if in flight, (this includes engines) • Flew numerous profiles including full • production flight test factory first flight profiles, as well as actual first flight profiles 23

Contingency Planning for First Flight • Perform all production system checks, engineering, • high

Contingency Planning for First Flight • Perform all production system checks, engineering, • high speed taxi/shimmy tests several days before first flight • • • Load nominal to forward c. g. /GW Leave APU running for takeoff Fuel to reach Edwards from end of flight Practice loss of all signaling capability to primary controls (have 2 roll spoilers, stabilizer available on cable) 24

Contingency Planning – cont’d • Hand held radio and GPS • Proof pressure test

Contingency Planning – cont’d • Hand held radio and GPS • Proof pressure test hydraulic system with • instrumentation installed to 3900 PSI (3000 normal) to build confidence for handling surge spikes • • • Bailout door aft of wing Concern over fuel gaging system Chase/photo (2 T 33, 1 T 38) Shadow flight in system integration 2 pilots on board, all other data transmitted to ground • Radio room staffed with experienced system experts 25

First Flight Readiness Indicators – number of events 1) “I thought you should know…”

First Flight Readiness Indicators – number of events 1) “I thought you should know…” 2) Test limitations and advisories 3) “Just this week we found…” 4) Media briefs 5) “Just in case the ___ doesn’t work remember…” 6) Engine ground runs (if new engine) 7) “Did you know that…” 26

Outcome So, How Did It Go? 27

Outcome So, How Did It Go? 27

Outcome • Just Fine! • Flew 3+48 • Completed production flight test systems tests

Outcome • Just Fine! • Flew 3+48 • Completed production flight test systems tests with no surprises (including engine shutdowns) • Initial HQ, flutter kicks, FBW reversion modes • Tailwind takeoff of 12 knots (Engine TB went to over 20 TW) • Instrumentation worked extremely well • Multiple chase worked reasonably well 28

29

29

Summary • Integration lab paid off in discoveries, flight test planning, safety, and in

Summary • Integration lab paid off in discoveries, flight test planning, safety, and in training the testers early • Flying test beds were invaluable in avoiding basic development work during validation/certification • We spent a lot of money • Next time we can do it for less (Delete) • An empowered and motivated work force can achieve miracles • First airplane entered commercial service in under one year from first flight (Five airplanes, 3700 hours) 30

Boeing 777 First Flight And the Days Before Any Questions? ? 31

Boeing 777 First Flight And the Days Before Any Questions? ? 31