-
Notifications
You must be signed in to change notification settings - Fork 1
/
flight-test-brevity-codes-sections.qmd
625 lines (353 loc) · 16 KB
/
flight-test-brevity-codes-sections.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
# Flight Test Brevity Codes {#sec-flighttestbrevity}
This appendix consists of flight test brevity codes that resolve many of the most common test team communication issues.
Codes are presented in roughly chronological order of a typical flight test mission.
The Type is shown in curly braces indicates whether a code is meant to:
- {D} Direct
- {I} Inform
- {R} Request
{{< pagebreak >}}
## RADIO CHECK
### Correct Usage {.unnumbered}
- "RADIO CHECK"
- "RADIO CHECK ON \[channel\]"
### Meaning {.unnumbered}
- {R} "RADIO CHECK"
- I'm requesting that you tell me how well you can hear my transmission on the PRIMARY or MAIN channel.\
- {R} "RADIO CHECK ON \[channel\]"
- I'm requesting that you tell me how well you can hear my transmission on the explicitly stated channel.
### Typical Errors {.unnumbered}
1. Calling for a "RADIO CHECK" from a channel other than PRIMARY or MAIN.
1. Calling for a "RADIO CHECK ON \[channel\]" from a channel other than that explicitly stated
### Effect of Errors {.unnumbered}
Aircrew think you're calling on a channel that you're not calling from, and provides a RADIO CHECK on that erroneous channel, leading to a "false positive" or "false negative."
### Plain English Antidote {.unnumbered}
"How do you hear me on \[channel\]?
{{< pagebreak >}}
## READY
### Correct Usage {.unnumbered}
"\[Transmitting callsign\] IS READY \[for taxi/departure/point X/etc\]"
### Meaning {.unnumbered}
{I} The sender is ready to support test as soon as clearance is obtained for the next administrative step (taxi, takeoff, etc.), or as soon as the receiver acknowledges with "\[Receiving callsign\] IS READY"
### Typical Error {.unnumbered}
1. "CLEARED TO \[action for which the sender has no authority or responsibility such as TAXI, DEPARTURE, APPROACH, etc.\]" 2. "…" (aka crickets)
### Effects of Error {.unnumbered}
1. Receiver begins action without proper coordination and/or clearance.
2. Aircrew are wondering what's going on.
### Plain English Antidotes {.unnumbered}
1. "\[Transmitting callsign\] is showing all necessary steps complete and is prepared for \[receiving callsign\] to \[take action\]"
2. Say something/anything.
{{< pagebreak >}}
## CLEARED
### Correct Usage {.unnumbered}
1. "CLEARED TO MANEUVER"
2. "CLEARED \[test point\]"
3. "CLEARED \[condition\]"
### Meaning {.unnumbered}
{D} Initiate action per the brief for this context
### Typical Errors {.unnumbered}
1. Saying "CLEARED TO MANEUVER" way too early, i.e. prior to setup, instead of clearing the aircrew to a setup flight condition to prepare for the actual maneuver.
2. Saying "CLEARED TO MANEUVER" way too late, i.e. the aircrew are waiting and burning gas, or they've already begun the maneuver without your clearance.
### Effects of Errors {.unnumbered}
1. Confusion ensues about if the test point has actually begun, if aircrew are on parameters, or if clearance has already been issued, requiring a conversation.
2. TC loses control of the mission and the trust/confidence of the aircrew because aircrew have gone rogue, not wanting to burn gas and time waiting for your clearance.
### Plain English Antidote {.unnumbered}
"We are on test point XX. We show good setup. The control room is ready. You are cleared to maneuver."
{{< pagebreak >}}
## STEP
### Correct Usage {.unnumbered}
"CLEARED CARD [card identifier] STEP [setup/procedure/recovery step identifier]"
### Meaning {.unnumbered}
{I} A way to clearly refer to a step in a setup, procedure, or recovery without explicitly describing the action. Often used to obfuscate test actions over unencrypted communications channels. Can also be used to avoid saying "special" words like "ABORT" if they are part of the procedure.
### Typical Errors {.unnumbered}
1. Saying the wrong step, or not indicating the card
2. Describing the actions explicitly
### Effects of Errors {.unnumbered}
1. Confusion and loss of situational awareness
2. Exposing test activities unnecessarily
### Plain English Antidotes {.unnumbered}
1. "We are on card [card identifier], complete step [step identifier]"
2. "We are on card [card identifier], complete step [step identifier]"
{{< pagebreak >}}
## CONCUR
### Correct Usage {.unnumbered}
"CONCUR"
### Meaning {.unnumbered}
{I} I have heard your proposed course of action and I agree with it.
### Typical Errors {.unnumbered}
1. "…" (crickets)
2. "CONFIRM"
3. "AFFIRMATIVE"
4. "COPY"
### Effects of Errors {.unnumbered}
1. Aircrew have no idea why they are waiting, if the radios are broken, and generally if you are still alive and breathing.
2. Answering a proposal with a request.
3. Answering a complicated proposal with a simple "yes"
4. Aircrew are left wondering you have any opinion.
### Plain English Antidote {.unnumbered}
"I agree"
{{< pagebreak >}}
## CONFIRM
### Correct Usage {.unnumbered}
"CONFIRM [declarative statement]"
### Meaning {.unnumbered}
{R} I am requesting that you reply with your understanding of something or with the current status of something.
### Typical Error {.unnumbered}
Convoluted verbiage
### Effects of Error {.unnumbered}
Confusion
### Plain English Antidote {.unnumbered}
"Is the [THING] in [STATE]?"
{{< pagebreak >}}
## CONTINUE
### Correct Usage {.unnumbered}
"CONTINUE"
### Meaning {.unnumbered}
{D} Keep going. (Alternative: I have heard you, but your concern can be addressed later.)
### Typical Errors {.unnumbered}
1. "…" (crickets)
2. "HOLD"
### Effects of Errors {.unnumbered}
1. Aircrew have no idea why they are waiting, if the radios are broken, and generally if you are still alive and breathing.
2. Aircrew confusion, since they may not be expecting to hold their current flight condition, or since they brought up a concern.
### Plain English Antidotes {.unnumbered}
1. Say something/anything.
2. "Keep doing what you're doing."
{{< pagebreak >}}
## AFFIRM
### Correct Usage {.unnumbered}
"AFFIRM"
### Meaning {.unnumbered}
{I} Yes
### Typical Errors {.unnumbered}
1. "ROGER"
2. "COPY"
3. "CONCUR"
4. "CONFIRM"
### Effects of Errors {.unnumbered}
1. Answering a question with "I heard you" brings things to a halt
2. Answering a question with "I heard you and have recorded what you said" brings things to a halt
3. Answering a question with "I have heard your proposed course of action and I agree with it" brings things to a halt
4. Answering a question with "I am requesting that you reply with your understanding of something or with the current status of something" brings things to a halt
### Plain English Antidote {.unnumbered}
"Yes"
{{< pagebreak >}}
## NEGATIVE
### Correct Usage {.unnumbered}
"NEGATIVE"
### Meaning {.unnumbered}
{I} No
### Typical Errors {.unnumbered}
See "AFFIRM"
### Effects of Errors {.unnumbered}
See "AFFIRM"
### Plain English Antidotes {.unnumbered}
"No"
{{< pagebreak >}}
## ACKNOWLEDGE
### Correct Usage {.unnumbered}
"ACKNOWLEDGE"
### Meaning {.unnumbered}
{R} I have updated something and am requesting verbal acknowledgement from all players.
### Typical Error {.unnumbered}
"…" (crickets)
### Effects of Error {.unnumbered}
1. You don't know that the test team has heard the update
1. The test team doesn't know you have heard the update.
### Plain English Antidotes {.unnumbered}
1. Repeat the transmission and request acknowledgement.
1. Repeat back the transmission verbatim: "The control room copies new floor 10K."
{{< pagebreak >}}
## WHEN ABLE
### Correct Usage {.unnumbered}
"WHEN ABLE"
### Meaning {.unnumbered}
{R} It sounds like you're busy, but I've got something to discuss, so get back to me when you can talk
### Typical Error {.unnumbered}
Talking over or into a busy pilot's conversation/thought process
### Effect of Error {.unnumbered}
Increased frustration
### Plain English Antidote {.unnumbered}
"I've got a question/piece of information when you have a chance.""
{{< pagebreak >}}
## STANDBY
### Correct Usage {.unnumbered}
"STANDBY"
### Meaning {.unnumbered}
{I} I have heard you, but I'm unable to reply to your transmission in detail at this time. In a moment, I will say more.
### Typical Errors {.unnumbered}
1. "…" (crickets)
2. "HOLD"
### Effects of Errors {.unnumbered}
1. Aircrew have no idea why they are waiting, if the radios are broken, and generally if you are still alive and breathing. Also waste of gas/resources as aircrew come off conditions.
2. Aircrew confusion, since they may not be expecting to hold their current flight condition
### Plain English Antidotes {.unnumbered}
1. Say something/anything.
2. "Wait a moment while we discuss."
{{< pagebreak >}}
## HOLD
### Correct Usage {.unnumbered}
"HOLD"
### Meaning {.unnumbered}
{D} Maintain current conditions until further notice.
### Typical Errors {.unnumbered}
1. "…" (crickets)
2. "STANDBY"
### Effects of Errors {.unnumbered}
1. Aircrew have no idea why they are waiting, if the radios are broken, and generally if you are still alive and breathing
2. Aircrew confusion, since they may not be expecting to be told to wait for you to get back to them.
### Plain English Antidotes {.unnumbered}
1. Say something/anything.
2. "Keep doing what you're doing." or "Stay on current conditions."
{{< pagebreak >}}
## …
### Correct Usage {.unnumbered}
"…"
### Meaning {.unnumbered}
{I} A pause between transmissions to allow the test team to interject. Often used in countdowns to irreversible events.
### Typical Errors {.unnumbered}
1. Holding the transmission key for the full duration of the countdown
2. Too short of a pause
### Effects of Errors {.unnumbered}
1. The test team cannot interject to prevent mistaken triggering of the irreversible event
2. The aircrew don't have time to listen for interjections
### Plain English Antidotes {.unnumbered}
1. "…"
2. (waiting long enough to listen for test team inputs)
{{< pagebreak >}}
## INCREASE/DECREASE
### Correct Usage {.unnumbered}
"[INCREASE/DECREASE] [PARAMETER]"
### Meaning {.unnumbered}
{D} Per the brief and the mission materials, the parameter is about to go out of tolerance/limits unless you comply with this advisory call.
### Typical Errors {.unnumbered}
1. "CHECK/WATCH [PARAMETER]"
2. "…" (crickets)
### Effects of Errors {.unnumbered}
1. Aircrew doesn't know what you want after they look at the parameter. The parameter probably dropped out of their scan, which necessitated the call in the first place, so they aren't aware of the corrective action.
2. Test point needs to be repeated, test limits are exceeded, aircraft limits are exceeded.
### Plain English Antidotes {.unnumbered}
1. "Your [PARAMETER] is approaching [TOLERANCE/LIMIT]."
2. Say something/anything.
### CAVEAT
This phrasing is up for debate, and this standard is provided as a baseline. If the test team deviates from the baseline, they should do so explicitly and intentionally.
{{< pagebreak >}}
## CEASE
### Correct Usage {.unnumbered}
- CEASE LASER
- CEASE FIRE
- CEASE TEST
### Meaning {.unnumbered}
{D} Discontinue the stated activity
### Typical Errors {.unnumbered}
- "CEASE" (without specifying what activity to discontinue)
- "STOP" (without specifying what activity to discontinue)
### Effects of Errors {.unnumbered}
- Confusion about what to discontinue
- Discontinue the wrong activity
- Continuing the activity
### Plain English Antidotes {.unnumbered}
- "Turn off [system]"
- "Stop doing [activity]"
{{< pagebreak >}}
## ABORT/KNOCK-IT-OFF
### Correct Usage {.unnumbered}
- "ABORT ABORT ABORT"
- "KNOCK-IT-OFF"
Example:
- Project: "ABORT ABORT ABORT"
- Quell 1: ""Quell 1 ABORT""
- Quell 2: ""Quell 2 ABORT""
- Project: ""Project ABORT, [REASON]"
### Meaning {.unnumbered}
{D} Per the brief and the mission materials, stop what you're doing and take corrective action.
### Typical Errors {.unnumbered}
1. Not reacting per the brief
2. The originator not saying the reason for the call.
### Effect of Errors {.unnumbered}
Confusion during time-critical events
### Plain English Antidotes {.unnumbered}
1. Because of the urgent nature of these calls, it's better to say the wrong thing than to say nothing. The best this is to practice the calls in the brief and over the radio prior to beginning test execution.
2. Say something/anything.
### NOTE
Which specific term to use depends on the test team's prior experience, the organization's norms, and the context. There are examples of "Terminate" being used on some test ranges as the word to signal the Flight Termination System, negating the test and possibly exposing the aircrew to additional hazards.
Abrupt test point cessation calls should be rehearsed in the brief, and in the air prior to testing, to establish the norm for the day.
{{< pagebreak >}}
## COMPLETE
### Correct Usage {.unnumbered}
- "RUN COMPLETE"
- "POINT COMPLETE"
- "CARD COMPLETE"
- "MISSION COMPLETE"
### Meaning {.unnumbered}
{I} The referenced set (RUN/POINT/CARD/MISSION) was executed within the success criteria per the brief and mission materials. No further action for the referenced set is required or desired.
In the case of MISSION COMPLETE, the data, fuel, aircraft, or formation requires that the test portion of the mission must conclude.
### Typical Errors {.unnumbered}
1. Saying "COMPLETE" before you know if execution was successful.
2. Saying "COMPLETE" before the set was finished.
3. Saying "COMPLETE" when what you really mean is "TERMINATE/ABORT/KNOCK-IT-OFF"
4. "…" (crickets)
5. Instead of "MISSION COMPLETE," "CLEARED TO RTB"
### Effects of Errors {.unnumbered}
1. Either you're lucky and the set was actually complete, or you have to eat your words and call for a repeat because the set was not, in fact, complete.
2. The aircrew cease execution prior to completion, negating the data and wasting millions of dollars of taxpayer money.
3. The aircrew aren't aware that something is wrong and continue with the test, possibly repeating the mistake or exceeding a limit.
4. Bueller?... Bueller?... Bueller?
5. ATC hears "RTB" and begins coordination before the aircrew are ready.
### Plain English Antidotes {.unnumbered}
1. "Standby for data review."
2. Say nothing until the set is complete.
3. "Mach/airspeed/altitude out of parameters. We'll need to repeat that point."
4. "The control room is satisfied with this run/point/card/mission."
5. See 4.
{{< pagebreak >}}
## NEXT
### Correct Usage {.unnumbered}
"NEXT [POINT/CARD/FLIGHT CONDITION]"
### Meaning {.unnumbered}
{I} The next thing is…
### Typical Error {.unnumbered}
"…" (crickets)
### Effects of Error {.unnumbered}
Two effects, depending on aircrew.
1. Either the aircrew wait and wonder what’s next, or
2. the aircrew declare what’s next and the control room loses control of the mission.
### Plain English Antidote {.unnumbered}
"Next point is X, at X feet and X Mach/KCAS."
{{< pagebreak >}}
## CLEAN AND DRY
### Correct Usage {.unnumbered}
- "REQUEST CLEAN AND DRY"
- "CHASE SHOWS YOU CLEAN AND DRY"
### Meaning {.unnumbered}
{I} Extends the concept of a "battle damage check" which is looking for "clean" meaning no visible damage and "dry" meaning no visible fluid leaks.
In flight test, "clean" can also mean no excessive door and/or panel gaps, no missing fasteners, or any other mechanical change from the previous check. Often made after gear retraction, before and after a high speed test point, prior to aerial refueling after high load or flutter test, and before returning to base.
### Typical Errors {.unnumbered}
None
### Effects of Errors {.unnumbered}
None
### Plain English Antidotes {.unnumbered}
None
{{< pagebreak >}}
## Codes NOT to use
1. ROGER
2. COPY
3. WILCO
They all leave out a very important factor. WHAT is being received, received and written, or complied with.
Better to be explicit.
1. "I understand" And better "I understand [then say what you understand]"
2. Read back what you just heard
3. "I will [do the thing you just requested]"
<!--# This is the section template
## CODE
### Correct Usage {.unnumbered}
"CODE"
### Meaning {.unnumbered}
Meaning
### Typical Errors {.unnumbered}
Typical errors
### Effects of Errors {.unnumbered}
Effects of errors
### Plain English Antidotes {.unnumbered}
Plain English Antidotes
{{< pagebreak >}}
-->