1
Ten Steps toEffective Preflight Briefing
and Efficient Test Execution
Mr. Kevin RansfordLCDR Brian Sandberg
3
• Understand exactly what you are looking for with regard to data in a way that you can explain to the aircrew
• Be sure that this is the basis on which your flight cards are written and prioritized
• Stop to think about this …– This is a big percentage of what your job as
an FTE is about
STEP 1:Know the system andthe purpose of the test
4
• If you are unsure, ask– It’s a characteristic of good judgment– No one is omniscient
• Anticipate questions on how it’s supposed to work, why it works that way, etc.
• Not knowing the answers - and you will never know all - will happen from time to time – Handle it maturely
STEP 1:Know the system andthe purpose of the test
5
• Test Data Required• Test Techniques
– Use resources like • SETP.org• SFTE.org• TPS Flight Test Manuals• People
• Aircrew Tasks– Checklists– Configurations/Altitudes/Airspeeds
STEP 2:Prepare the Test Cards
6
• If there is an interpretation problem with the test plan… …then stop and seek advice from the next level in
the chain of command
• Make sure that your current flight clearance and test plan match the test cards!
• Make them simple to understand and use– Anyone can make something complicated
STEP 2:Prepare the Test Cards
7
• To develop the level of understanding between two people of different backgrounds
• To add the “pilot slant” to how things are worded, ordered, and interpreted
• If necessary, add keystroke/switchology sequence to help the aircrew
STEP 3:Have a Project Pilot
Review the Test Cards
8
• To see if s/he can read and use them– Font size, room for comments, etc
• If possible, use a simulator or task trainer– Highly recommended tests which may present
unusual or considerable hazards or require extensive crew coordination
• Remember “crew” includes the TM room and Chase
STEP 3:Have a Project Pilot
Review the Test Cards
11
• Determine when and where well beforehand and verify the reservation– Guest users sometimes get preempted
• What does your test event require in a meeting place?– Computer/Projector/Audio?
• Spread the Word– Flight Schedule/MS Outlook Meeting Maker
STEP 4:Find a Location
12
• Make sure you have the right representatives– Range, TM, contractors, maintenance?– Specially trained/experienced aircrew
• For new systems operation or critical test
– Specially trained/experience test conductors• Don’t assign the most junior guy the most critical
task/parameters
STEP 5:Assemble the
Proper Personnel
13
• If you don’t know how to read and interpret it then ask someone you trust to show you
• Verify that there are no outstanding configuration approval or flight clearance (airworthiness release) issues
– Was the configuration (hardware or software) changed? Is it still installed in the aircraft?
• Fuel load/cg/weight, etc. are all there waiting for you to record
STEP 6:Review the ADB/781’s
14
• Note and brief anomaly trends in the behavior of a certain system or component:– Examples:
• Radio #2 has poor reception• Frequent Mission Computer reboots
• Note and brief maintenance items that require a re-check during this flight– Might delay the test
STEP 6:Review the ADB/781’s
17
• This will ensure that all critical items are discussed during the test brief
• The checklist and your brief should include the following, at a minimum:– Overview of the flight and test sequence– Identify the aircrew for the test aircraft and
any chase aircraft– Identify the project lead engineer– Which aircraft?– Configuration under test
STEP 7:Use a Checklist
18
• Include, at a minimum (continued):– Changes in configuration since last test– Specific methods, procedures, and data
required.– Recent maintenance actions– Fuel load/fuel tank configuration– Any store configuration or other externals– Ground support required/available– Communications frequencies, including
backups
STEP 7:Use a Checklist
19
• Include, at a minimum (continued):– COMSEC requirements and procedures– Key communications concepts (green range,
cleared hot, abort, etc.)– Operating area – Weather, include terminal and operating area
forecasts • if necessary, with potential volatile weather
conditions, call the forecaster
STEP 7:Use a Checklist
20
• Include, at a minimum (continued):– Range times– Sunset/moonrise– Special precautions/Threat Hazard Analysis
items– Test limitations/aircraft limitations (Flight
Clearance)
STEP 7:Use a Checklist
21
• Include, at a minimum (continued):– Go / No-Go items – Knock-it-off and Abort criteria and procedures– Ordnance procedures– Instrumentation procedures
• Including preflight requirements
– Search and Rescue requirements and status
STEP 7:Use a Checklist
24
• Be punctual
• Minimize distractions
• Silence the cell phones
• Make sure all aircrew and supporting staff have a copy of the flight cards
STEP 8:Take Charge, Run the Brief
25
• Ensure that those in the briefing room are quiet unless they are questioned or have something timely/critical to add– Start with the brief sheet items, it will provide
the initial structure to your brief and answer a lot of questions
STEP 8:Take Charge, Run the Brief
26
• As the project engineer, it is your job to run the brief and answer aircrew and supporting team questions– If you don’t know the answer, defer the
question to someone in the room who does– If the answer is required for the event then
take the appropriate action at the proper time
– Your audience is Type A, your demeanor should reflect that same level of attention, dedication, and professionalism.
– Remember, this is your project
STEP 8:Take Charge, Run the Brief
27
• Always emphasize the responsible NO VOTE – The NO VOTE can be executed:
• By anyone • At any time
– During the brief– During the preflight– During the flight
• In areas not specifically addressed in the test plan – e.g., “tempo”,weather conditions, personal factors
STEP 8:Take Charge, Run the Brief
28
• Review the Test Hazards and Safety Checklist, particularly with new test team members– Point out what are the most likely hazards which
might be encountered during this test.– Ensure the crew understands the “why” and, as
applicable, has rehearsed the “how” of getting back into a safe condition
– Aside from the NATOPS/-10 brief, always review emergency procedures related to the test/equipment
STEP 8:Take Charge, Run the Brief
31
• If you have had a lot of previous experience with the system under test -- share it– Discuss anomalies and idiosyncrasies of the
system– Discuss what intuition and experience are telling
you about what you have tested to date
• DO NOT ASSUME everyone at the brief will understand the fundamentals of the test/equipment or the data obtained and analyzed to date
STEP 8:Take Charge, Run the Brief
33
• Don’t demonstrate your superior knowledge or skill, just execute the test– “Hey Bubba…”
• Don’t change items during the flight to conduct a science project
• If you deviate from the cards and/or the brief……it’s very likely you violated the test plan, flight
clearance, and professional good judgment
STEP 9:You’re sick of hearing it,
but FLY THE BRIEF!
34
• In the TM room/range control– Good judgment/temperament/
communications discipline is mandatory– Assign one person to talk to the aircraft
STEP 9:You’re sick of hearing it,
but FLY THE BRIEF!
35
• What was accomplished• What could not be completed and why
– Lack of time, poor performance, etc.
• Follow-up actions• Discuss and document system deficiencies• Discuss any lessons learned• Suggest ways to improve the process
STEP 10:Timely Postflight Debrief
36
In Summary
• Study the System Under Test• Prepare Test Cards• Pilot Review of Test Cards• Acquire a Location to Brief• Assemble Appropriate Personnel• Review Aircraft Maintenance Record• Use a Checklist• Run the Brief• Fly the Cards• Debrief
Recommended