15J0195 Saudi JDAM - 34 Source Data 1 May 15
15J0195 Saudi JDAM - 34 Source Data 1 May 15
DISTRIBUTION STATEMENT E:
Distribution authorized to the Department of Defense, Administrative or Operational Use, May 1,
2015. Other requests shall be referred to ACC/EBDJ, 205 West D. Avenue, Bldg 350, Suite 135, Eglin
AFB, FL 32542-6848.
Destruction Notice – Destroy by any method that will prevent disclosure of contents or
reconstruction of the document and/or media.
Boeing Report 15J0089
1 May 2015
SOURCE DATA
FOR
B
Boeing Report 15J0089
1 May 2015
Table of Contents
EXECUTIVE SUMMARY 1
i
Boeing Report 15J0089
1 May 2015
ii
Boeing Report 15J0089
1 May 2015
APPENDIX A: LJDAM SOURCE DATA FOR SLICK ADE FOR STANDARD JDAM
INTERFACE (GROUND RANGE) 152
A.1 Slick ADE Energy Capability Curves 152
A.2 Slick ADE LJDAM Rules of Thumb Tables (Ground Range) 157
A.2.1 Slow (0-40 MPH) and Fast (40-70 MPH) Mover Ground Range ROT Tables 157
A.2.2 Slow Walker (0-10 MPH) Ground Range ROT Tables 169
A.2.3 Low HAT & Dive (0-40 MPH) Ground Range ROT Tables 175
A.3 Slick ADE LJDAM Footprint Example 180
APPENDIX B: LJAM SOURCE DATA USING SLICK ADE FOR STANDARD JDAM
INTERFACE (SLANT RANGE) 188
B.1 Slick ADE Energy Capability Curves 188
B.2 Slick ADE LJDAM Rules of Thumb Tables (Slant Range) 193
B.2.1 Slow (0-40MPH) and Fast (40-70MPH) Mover Slant Range ROT Tables 193
B.2.2 Slow Walker (0-10MPH) Slant Range ROT Tables 205
B.2.3 Low HAT & Dive (0-40 MPH) Slant Range ROT Tables 211
B.3 Slick ADE LJDAM Footprint Examples 216
APPENDIX C: LDAM SOURCE DATA USING CENTERED ADE FOR STANDARD JDAM
INTERFACE 224
C.1 Centered ADE Energy Capability Curves 224
C.2 Centered ADE LJDAM Rules of Thumb Tables (Ground Range) 229
C.2.1 Slow (0-40 MPH) and Fast (40-70 MPH) Movers ROT Tables 229
C.2.2 Slow Walker (0-10MPH) ROT Tables 241
C.3 Centered ADE LJDAM Footprint Examples 247
iii
Boeing Report 15J0089
1 May 2015
iv
Boeing Report 15J0089
1 May 2015
v
Boeing Report 15J0089
1 May 2015
FIGURE 8.71 - GBU-38 SERIES (SLICK WARHEAD/SLICK ADE) COMMANDED AZIMUTH DELIVERY........... 129
FIGURE 8.72 - GBU-38 SERIES (SLICK WARHEAD/SLICK ADE) TARGET ALTITUDE DELIVERY .................. 130
FIGURE 8.73 - GBU-38 SERIES (SLICK WARHEAD/SLICK ADE) WINDS ON DELIVERY – 59 KTS ................. 131
FIGURE 8.74 - GBU-38 SERIES (SLICK WARHEAD/SLICK ADE) WINDS ON DELIVERY – 119KTS ................ 132
FIGURE 8.75 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) LEVEL DELIVERY - 10KFT133
FIGURE 8.76 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) LEVEL DELIVERY - 20KFT134
FIGURE 8.77 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) LEVEL DELIVERY - 30KFT135
FIGURE 8.78 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) LEVEL DELIVERY - 40KFT136
FIGURE 8.79 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) LEVEL DELIVERY - 50KFT137
FIGURE 8.80 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) LOFT DELIVERY........... 138
FIGURE 8.81 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) DIVE DELIVERY ........... 139
FIGURE 8.82 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) WITH & WITHOUT IMPACT
CONSTRAINTS ON DELIVERY ................................................................................................................ 140
FIGURE 8.83 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) COMMANDED AZIMUTH
DELIVERY ............................................................................................................................................ 141
FIGURE 8.84 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) TARGET ALTITUDE
DELIVERY ............................................................................................................................................ 142
FIGURE 8.85 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) WINDS ON DELIVERY -
59KTS ................................................................................................................................................... 143
FIGURE 8.86 - GBU-38 SERIES (SLICK OR THERMAL WARHEAD/CENTERED ADE) WINDS ON DELIVERY - 119
KTS ....................................................................................................................................................... 144
FIGURE 8.87 – GENERAL DERATING OF A GBU-38 JDAM LAR FOR GBU-54 LJDAM .............................. 146
FIGURE 8.88 - GBU-54 STATIONARY TARGET DAY TYPE COMPARISON, COLD / POLAR ............................. 147
FIGURE 8.89 - GBU-54 STATIONARY TARGET DAY TYPE COMPARISON, HOT / TROPICAL .......................... 148
FIGURE 8.90 - GBU-54 STATIONARY TARGET WIND SPEED VARIATION, 0 DEG WINDS .............................. 148
FIGURE 8.91- GBU-54 STATIONARY TARGET WIND SPEED VARIATION, 90 DEG WINDS ............................. 149
FIGURE 8.92 - GBU-54 STATIONARY TARGET WIND SPEED VARIATION, 180 DEG WINDS .......................... 149
FIGURE 8.93 - GBU-54 STATIONARY TARGET WIND SPEED VARIATION, 270 DEG WINDS .......................... 150
FIGURE 8.94 - GBU-54 STATIONARY TARGET WIND DIRECTION VARIATION, 100 KT WINDS ..................... 150
FIGURE 8.95 - GBU-54 STATIONARY TARGET, TARGET ALTITUDE VARIATION, NO VELOCITY BIAS, HAT =
20 KFT, IMPACT ANGLE = 70 DEG, TALT = 0, 2, 5 AND 10 KFT ............................................................ 151
FIGURE 8.96 - GBU-54 STATIONARY TARGET, TARGET ALTITUDE VARIATION, NO VELOCITY BIAS, HAT =
30 KFT, IMPACT ANGLE = 70 DEG, TALT = 0, 2, 5 AND 10 KFT ............................................................ 151
FIGURE A.1 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 0
KFT MSL TARGET ALTITUDE .............................................................................................................. 152
FIGURE A.2 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 153
FIGURE A.3 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 153
FIGURE A.4 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 0
KFT MSL TARGET ALTITUDE .............................................................................................................. 154
FIGURE A.5 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 154
FIGURE A.6 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 155
FIGURE A.7 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 0
KFT MSL TARGET ALTITUDE .............................................................................................................. 155
FIGURE A.8 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 156
vi
Boeing Report 15J0089
1 May 2015
FIGURE A.9 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 156
FIGURE A.10 – GBU-54 STATIONARY TARGET, ALTITUDE = 15 KFT, IMPACT ANGLE = 70 DEG .................. 181
FIGURE A.11 – GBU-54 STATIONARY TARGET, ALTITUDE = 25 KFT, IMPACT ANGLE = 70 DEG .................. 181
FIGURE A.12 – GBU-54 STATIONARY TARGET, ALTITUDE = 25 KFT, IMPACT ANGLE = 90 DEG .................. 182
FIGURE A.13 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 15 KFT, (70 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 182
FIGURE A.14 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 15 KFT, BIAS SPEED = 40 MPH (68
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 183
FIGURE A.15 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 25 KFT, (90 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 183
FIGURE A.16 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 25 KFT, BIAS SPEED = 40 MPH (83
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 184
FIGURE A.17 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 35 KFT, (70 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 184
FIGURE A.18 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 40 MPH (83
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 185
FIGURE A.19 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 10 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 50 MPH ................................................................ 185
FIGURE A.20 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 15 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 186
FIGURE A.21 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 25 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 186
FIGURE A.22 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 60 MPH (84
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 70 MPH ................................................................ 187
FIGURE A.23 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 187
FIGURE B.1 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 0
KFT MSL TARGET................................................................................................................................ 188
FIGURE B.2 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 189
FIGURE B.3 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 189
FIGURE B.4 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 0
KFT MSL TARGET ALTITUDE .............................................................................................................. 190
FIGURE B.5 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 190
FIGURE B.6 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 191
FIGURE B.7 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 0
KFT MSL TARGET ALTITUDE .............................................................................................................. 191
FIGURE B.8 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 192
FIGURE B.9 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 192
FIGURE B.10 – GBU-54 STATIONARY TARGET, ALTITUDE = 15 KFT, IMPACT ANGLE = 70 DEG .................. 217
FIGURE B.11 – GBU-54 STATIONARY TARGET, ALTITUDE = 25 KFT, IMPACT ANGLE = 70 DEG .................. 217
FIGURE B.12 – GBU-54 STATIONARY TARGET, ALTITUDE = 25 KFT, IMPACT ANGLE = 90 DEG .................. 218
vii
Boeing Report 15J0089
1 May 2015
FIGURE B.13 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 15 KFT, (70 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 218
FIGURE B.14 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 15 KFT, BIAS SPEED = 40 MPH (68
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 219
FIGURE B.15 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 25 KFT, (90 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 219
FIGURE B.16 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 25 KFT, BIAS SPEED = 40 MPH (83
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 220
FIGURE B.17 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 35 KFT, (70 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 220
FIGURE B.18 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 40 MPH (83
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 221
FIGURE B.19 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 10 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 50 MPH ................................................................ 221
FIGURE B.20 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 15 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 222
FIGURE B.21 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 25 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 222
FIGURE B.22 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 60 MPH (84
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 70 MPH ................................................................ 223
FIGURE B.23 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 223
FIGURE C.1 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 0
KFT MSL TARGET ALTITUDE .............................................................................................................. 224
FIGURE C.2 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 5
KFT MSL TARGET ALTITUDE .............................................................................................................. 225
FIGURE C.3 – ENERGY CAPABILITY CURVES FOR 0-40 MPH TARGETS, OMNI-DIRECTIONAL TARGET HDG 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 225
FIGURE C.4 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º
RELEASE 0 KFT MSL TARGET ALTITUDE ............................................................................................ 226
FIGURE C.5 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º
RELEASE 5 KFT MSL TARGET ALTITUDE ............................................................................................ 226
FIGURE C.6 – ENERGY CAPABILITY CURVES FOR 40-70 MPH TARGETS, TAIL CHASE CONDITION OF ±45º
RELEASE 10 KFT MSL TARGET ALTITUDE .......................................................................................... 227
FIGURE C.7 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º
RELEASE 0 KFT MSL TARGET ALTITUDE ............................................................................................ 227
FIGURE C.8 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º
RELEASE 5 KFT MSL TARGET ALTITUDE ............................................................................................ 228
FIGURE C.9 – ENERGY CAPABILITY CURVES FOR 40-50 MPH TARGETS, TAIL CHASE CONDITION OF ±45º 10
KFT MSL TARGET ALTITUDE .............................................................................................................. 228
FIGURE C.10 – GBU-54 STATIONARY TARGET, ALTITUDE = 15 KFT, IMPACT ANGLE = 70 DEG .................. 248
FIGURE C.11 – GBU-54 STATIONARY TARGET, ALTITUDE = 25 KFT, IMPACT ANGLE = 70 DEG .................. 248
FIGURE C.12 – GBU-54 STATIONARY TARGET, ALTITUDE = 25 KFT, IMPACT ANGLE = 90 DEG .................. 249
FIGURE C.13 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 15 KFT, (70 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 249
FIGURE C.14 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 15 KFT, BIAS SPEED = 40 MPH (68
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 250
FIGURE C.15 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 25 KFT, (90 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 250
viii
Boeing Report 15J0089
1 May 2015
FIGURE C.16 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 25 KFT, BIAS SPEED = 40 MPH (83
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 251
FIGURE C.17 – GBU-54 MOVING TARGET, NO VELOCITY BIAS, ALTITUDE = 35 KFT, (70 DEG IMPACT ANGLE
COMMAND), TARGET SPEED = 15 MPH ................................................................................................. 251
FIGURE C.18 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 40 MPH (83
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 35 MPH ................................................................ 252
FIGURE C.19 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 10 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 50 MPH ................................................................ 252
FIGURE C.20 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 15 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 253
FIGURE C.21 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 25 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 253
FIGURE C.22 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 60 MPH (84
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 70 MPH ................................................................ 254
FIGURE C.23 – GBU-54 MOVING TARGET, VELOCITY BIAS, ALTITUDE = 35 KFT, BIAS SPEED = 60 MPH (69
DEG IMPACT ANGLE COMMAND), TARGET SPEED = 60 MPH ................................................................ 254
ix
Boeing Report 15J0089
1 May 2015
Index of Tables
x
Boeing Report 15J0089
1 May 2015
TABLE A.6 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 20
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 164
TABLE A.7 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 40
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 165
TABLE A.8 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 60
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 166
TABLE A.9 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 80
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 167
TABLE A.10 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 100
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 168
TABLE A.11 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 20
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 170
TABLE A.12 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 40
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 171
TABLE A.13 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 60
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 172
TABLE A.14 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 80
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 173
TABLE A.15 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 100
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 174
TABLE A.16 - LJDAM GROUND RANGE RELEASE LOW HAT ROT FOR 0–40 MPH FOR WINDS UP TO 20
KNOTS .................................................................................................................................................. 176
TABLE A.17 - LJDAM GROUND RANGE RELEASE LOW HAT ROT FOR 0–40 MPH FOR WINDS UP TO 40
KNOTS .................................................................................................................................................. 177
TABLE A.18 - LJDAM GROUND RANGE RELEASE LOW HAT ROT FOR 0–40 MPH FOR WINDS UP TO 60
KNOTS .................................................................................................................................................. 178
TABLE A.19 - LJDAM GROUND RANGE RELEASE LOW HAT ROT FOR 0–40 MPH FOR WINDS UP TO 80
KNOTS .................................................................................................................................................. 179
TABLE A.20 – LIST OF LJDAM EXAMPLE FOOTPRINTS (SLICK ADE, MACH 0.70-0.95) ............................. 180
TABLE B.1- LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 20 KNOTS
(SLICK ADE, MACH 0.70-0.95) ............................................................................................................ 195
TABLE B.2 – LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 40
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 196
TABLE B.3 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 60 KNOTS
(SLICK ADE, MACH 0.70-0.95) ............................................................................................................ 197
TABLE B.4 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 80 KNOTS
(SLICK ADE, MACH 0.70-0.95) ............................................................................................................ 198
TABLE B.5 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 100
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 199
TABLE B.6 – LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 20
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 200
TABLE B.7 – LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 40
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 201
TABLE B.8 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 60
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 202
TABLE B.9 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 80
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 203
TABLE B.10 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 100
KNOTS (SLICK ADE, MACH 0.70-0.95) ................................................................................................ 204
xi
Boeing Report 15J0089
1 May 2015
TABLE B.11 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 20
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 206
TABLE B.12 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 40
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 207
TABLE B.13 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 60
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 208
TABLE B.14 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 80
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 209
TABLE B.15 - LJDAM SLANT RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 100
KNOTS (SLICK ADE, 0.70-0.95M) ....................................................................................................... 210
TABLE B.16 - LJDAM SLANT RANGE RELEASE LOW HAT ROT FOR 0 – 40 MPH FOR WINDS UP TO 20
KNOTS .................................................................................................................................................. 212
TABLE B.17 - LJDAM SLANT RANGE RELEASE LOW HAT ROT FOR 0 – 40 MPH FOR WINDS UP TO 40
KNOTS .................................................................................................................................................. 213
TABLE B.18 - LJDAM SLANT RANGE RELEASE LOW HAT ROT FOR 0 – 40 MPH FOR WINDS UP TO 60
KNOTS .................................................................................................................................................. 214
TABLE B.19 - LJDAM SLANT RANGE RELEASE LOW HAT ROT FOR 0 – 40 MPH FOR WINDS UP TO 80
KNOTS .................................................................................................................................................. 215
TABLE B.20 – LIST OF LJDAM EXAMPLE FOOTPRINTS (SLICK ADE, MACH 0.70-0.95) ............................. 216
TABLE C.1- LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 20
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 231
TABLE C.2 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 40
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 232
TABLE C.3 - LJDAM GROUND RANGE FOR 0 – 40 MPH FOR WINDS UP TO 60 KNOTS ................................ 233
TABLE C.4 LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 80
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 234
TABLE C.5 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 40 MPH FOR WINDS UP TO 100
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 235
TABLE C.6 - LJDAM GROUND RANGE FOR 40 – 70 MPH FOR WINDS UP TO 20 KNOTS .............................. 236
TABLE C.7 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 40
KNOTS (CENTERED ADE, 0.70-095M) ................................................................................................. 237
TABLE C.8 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 60
KNOTS (CENTERED ADE, 0.70-095M) ................................................................................................. 238
TABLE C.9 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 80
KNOTS (CENTERED ADE, 0.70-095M) ................................................................................................. 239
TABLE C.10 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 40 – 70 MPH FOR WINDS UP TO 100
KNOTS (CENTERED ADE, 0.70-095M) ................................................................................................. 240
TABLE C.11 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 20
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 242
TABLE C.12 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 40
KNOTS .................................................................................................................................................. 243
TABLE C.13 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 60
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 244
TABLE C.14 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 80
KNOTS (CENTERED ADE, 0.70-0.95M) ................................................................................................ 245
TABLE C.15 - LJDAM GROUND RANGE RELEASE RULE OF THUMB FOR 0 – 10 MPH FOR WINDS UP TO 100
KNOTS (CENTERED ADE) .................................................................................................................... 246
TABLE C.16 – LIST OF LJDAM EXAMPLE FOOTPRINTS (CENTERED ADE) .................................................. 247
xii
Boeing Report 15J0089
1 May 2015
FOREWORD
PURPOSE AND SCOPE
This document has been prepared to provide unclassified supplemental aircrew weapon delivery source
data associated with the Joint Direct Attack Munition (JDAM) and the Laser JDAM (LJDAM). This
document provides descriptive information and aircrew procedures for the GBU-31, GBU-38 and GBU-54
series Guided Bomb Units. The procedural support data contained in this document is to be used as source
data for the preparation of updates to the aircrew weapons manual. This information is general information
related to the JDAM weapon and does not contain procedures for any specific aircraft. This document
contains source data that can be used for manual mission planning as well as weapon employment
restrictions and guidelines. The GBU-54 consists of a GBU-38 JDAM with the addition of a field-installed
DSU-38/B Laser Kit. This document contains information relevant to the GBU-54 manual mode of
operation which utilizes a standard GBU-38 JDAM aircraft to weapon interface and Rule-of-Thumb (ROT)
data for weapon employment. This manual does not contain LJDAM In Weapon LAR (IWL) data but does
contain a brief description of the LJDAM laser interface and employment guidelines using the LJDAM
IWL.
xiii
Boeing Report 15J0089
1 May 2015
List of Acronyms/Abbreviations
Acronym/Abbreviation Definition
6DOF Six Degrees of Freedom
A/C Aircraft
ACQ Acquisition
ADE Air Data Estimator
AFMSS Air Force Mission Support System
AGL Above Ground Level
align alignment
Alt Altitude
AOA Angle-of-Attack
AOU Area of Uncertainty
ASIC Application-Specific Integrated Circuit
AUR All Up Round
A/W/E Aircraft/Weapon/Electronic
Az Azimuth
BIT Built In Test
BOC Bomb-On-Coordinate
CAS Close Air Support
C/A (code) Coarse Acquisition
CAT Category
CDE Classified Data Erase
CEP Circular Error Probable
CMBRE Common Munitions BIT/Reprogramming Equipment
Cmd Command
CNM Complementary Navigation Message
CONOPS Concept of Operations
CPU Central Processor Unit
CR Crossrange
CTL Current Target Location LAR
CTS Commit to Separate
CTSS Committed to Store Separation
DC Direct Current
DEG Degrees
DMPI Desired Mean Point of Impact
DR Downrange
DSU Direct Service Unit
DTC/DTD/DTE Data Transfer Cartridge/Device/Equipment
ECIU Enhanced Central Interface Unit
EGM Earth Gravity Model
F Fahrenheit
FFCS Fuze Function Control System
FLD Fin Lock Device
FLIR Forward Looking Infrared
FMU Fuze Munition Unit
FOM Figure Of Merit
FOV Field of View
FRPA Fixed Reception Pattern Antenna
ft feet
FWD Forward
FZU Fuze Initiator Unit
xiv
Boeing Report 15J0089
1 May 2015
List of Acronyms/Abbreviations
Acronym/Abbreviation Definition
G acceleration in terms of gravity
GBU Guided Bomb Unit
GCU Guidance Control Unit
GFAC Ground Forward Air Controller
GPS Global Positioning System
GPSRM Global Positioning System Receiver Module
GPSSRM Global Positioning System SAASM Receiver Module
HAE Height Above Ellipsoid
HAT Height Above Target
HOW Handover Word
HW Hardware
Hz Hertz (i.e. cycles per second)
ID Identification
IBIT Initiated Built In Test
ICD Interface Control Document
Imp Impact
IMU Inertial Measurement Unit
INS Inertial Navigation System
IWL In Weapon LAR
JDAM Joint Direct Attack Munition
JPF Joint Programmable Fuze
JTAC Joint Terminal Attack Control
KCAS Knots Calibrated Air Speed
kft thousand feet
km kilometer
KMU Kit Munition Unit
KTAS Knots True Air Speed
kts knots
LAR Launch Acceptable Region
Lat Latitude
LBSLN Laser Baseline
lbs Pounds
LDGP Low Drag General Purpose
LGB Laser Guided Bomb
LJDAM Laser JDAM
LLPL Long Last Pulse Logic
LMT Laser Moving Target
LOL Loss of Lock
Long Longitude
LOS Line of Sight
LTKS Laser Target Known Stationary
m meters
MARG Marginal
max. maximum
MDT Mass Data Transfer
MFD Multifunction Display
MFDS Multifunction Display Set
MIL-STD Military Standard
min. minutes
Min minimum
xv
Boeing Report 15J0089
1 May 2015
List of Acronyms/Abbreviations
Acronym/Abbreviation Definition
mj milli-joules
mph miles per hour
MRA Minimum Release Altitude
ms milliseconds
msec milliseconds
MSL Mean Sea Level
mux multiplex
NAV Navigation
NG No Go
nm nautical miles
nmi nautical miles
nsec nanoseconds
NSQ Navigation Solution Quality
NSTL Nose and Tail
OFP Operational Flight Program
P (code) Precision (code)
PBIT Periodic Built In Test
PDOP Position Dilution Of Precision
PRF Pulse Repetition Frequency
PTL Propagated Target Location LAR
PTAM Periodic Transfer Alignment Message
PTT Precision Target Tracker
QRC Quick Reaction Capability
rcvd received
rel release
RF Radio Frequency
RLG Ring Laser Gyro
RMS Root Mean Squared
ROT Rule of Thumb
RSS Root Sum Squared
RT Relative Targeting
R/T Receiver/Transmitter
SAASM Selective Availability Anti-Spoofing Module
SEC Seconds
SHOLS Single Hoist Ordnance Loading System
SIS Signal in Space
SLPL Short Last Pulse Logic
SMS Stores Management System
TAL Transfer Alignment Maneuver
TAS Tail Actuator Subsystem
TDA Target Density Altitude
TDS Target Data Set
tgt target
TKS Target Known Stationary
TLE Target Location Error
TM Telemetry
TOF Time of Fall or Time of Flight
T/O Take-off
TOO Target of Opportunity
xvi
Boeing Report 15J0089
1 May 2015
List of Acronyms/Abbreviations
Acronym/Abbreviation Definition
TOF Time of Flight
TSE Target State Estimator
TTFF Time to First Fix
TXA Transfer Alignment
UAI Universal Armament Interface
UNSAT Unsatisfactory
URA User Range Accuracy
V Volts
VDC Volts Direct Current
VAC Volts Alternating Current
Volt. Voltage
WGS World Geodetic System
WPN Weapon
wrt with respect to
Xfer Transfer
ZRF Zero Retention Force
xvii
Boeing Report 15J0089
May 1, 2015
EXECUTIVE SUMMARY
The Joint Direct Attack Munition (JDAM) is a joint service weapon which uses an onboard Global
Positioning System (GPS) aided Inertial Navigation System guidance set with MK 84, BLU-109 and MK
82 series warheads. When referring to these weapons collectively, the JDAM weapons may be referred to
as baseline JDAM. The guidance set, when combined with a warhead and an appropriate fuze, forms a
JDAM Guided Bomb Unit (GBU). The JDAM guidance set gives these bombs adverse weather capability
with much improved accuracy. The JDAM weapon can be delivered from standoff ranges at high or low
altitudes against a variety of land and surface targets during the day or night. After release, JDAM
autonomously guides to a target using the resident GPS-aided INS guidance system. A notional Concept of
Operations (CONOPS) is depicted in Figure E.1 with a Laser JDAM CONOPS depicted in Figure E.2.
JDAM is equipped with a MIL-STD-1760 interface and is capable of employment from various aircraft
platforms. The MIL-STD-1760 interface allows the aircraft to initialize and control the JDAM and program
the FMU-152 series Joint Programmable Fuze prior to release. Also, power, 1553 mux and discrete data are
transferred between the host aircraft and JDAM via the 1760 interface. The JDAM 1760 umbilical
connector allows support equipment to download software or to test the weapon.
JDAM is a bomb-on-coordinates (BOC) weapon which requires the input of accurate target coordinates.
Target coordinates can be transferred to the JDAM through mission planning data transfer devices (pre-
planned missions), through on-aircraft targeting systems (self-targeting) or manually through cockpit data
entry panels. In all cases, JDAM requires target coordinates in Latitude, Longitude and altitude. There are
three possible references for the target altitude: Mean Sea Level (MSL) based on the WGS-84 geoid height
table with 10 degree latitude/longitude spacing, MSL based on the Earth Gravitational Model 1996 geoid
height table with 15 minute latitude/longitude spacing, and Height Above Ellipsoid (HAE) referenced to
the WGS-84 Earth model.
JDAM accuracy is dependent upon the navigation mode. The primary navigation mode is GPS-aided and
means the JDAM navigation will be updated during free-flight with highly accurate GPS-aiding data. After
weapon launch, the GPS receiver quickly acquires and tracks satellites. Once the GPS receiver is in track
mode, it provides pseudorange and deltarange measurements to the JDAM mission computer, resulting in
precise weapon position and velocity. Total system accuracy for baseline JDAM with GPS-aiding against
horizontal targets for a 60 degree or higher impact angle is 5 meters Circular Error Probable (CEP). With
GPS-aiding, non-laser guided JDAM accuracy is primarily driven by the target location error (TLE). When
GPS signal denial is present, some GPS signals may be processed, but the geometry of the tracked satellites
may produce a poor GPS dilution of precision and the individual pseudorange measurements have
increased noise. As a result, the system accuracy for a baseline JDAM with GPS-aiding in a GPS signal
denial environment may degrade. When the weapon reports GPS signal denial levels of 1 or 2, the JDAM
will meet GPS performance in Table 8.1.
The backup navigation mode, INS-Only, means that no GPS measurement updates are available to the
JDAM during free-flight. JDAM INS-Only navigation accuracy is a function of aircraft handoff accuracy,
target location error, and IMU drift rate during weapon guidance to the target. INS-Only missions can
occur during short weapon times of flight (insufficient time to acquire and track GPS satellites) or when
operating in a GPS-denied environment (i.e. GPS jamming environment) and GPS satellite acquisition is
unsuccessful. Accuracy with INS-only navigation against horizontal targets with impact angles 60 degrees
or higher and flight times less than 100 seconds (on-axis) or 90 seconds (off-axis) is specified to be 30
meters CEP. INS-only accuracy is strongly influenced by weapon time of flight so the INS only accuracy
for the typical JDAM mission is much better than the 30 meter requirement. Flight test data indicates that
INS-only performance is better than specification, about 19 meters CEP for a 100 second flight and about 7
meters CEP for a 60 second flight when the aircraft provides a GPS quality position hand-off.
1
Boeing Report 15J0089
May 1, 2015
The GBU-54 Laser JDAM (LJDAM) provides precision laser guidance capability for improved accuracy
and enhanced reactive and mobile targeting capability to the baseline JDAM. The LJDAM consists of a
field installed DSU-38/B laser sensor assembly that is installed in the forward fuze well of a MK 82 bomb
body, along with a fuze and fuze accessories. An external wire harness connects the sensor assembly to the
KMU (Kit Munition Unit)-572 guidance set and tail assembly through the fuze access door. When
configured as an all-up-round (AUR), the weapon designation is GBU-54. The DSU-38/B enhances the
basic JDAM functionality of executing pre-planned fixed targets to include the ability to execute lased
fixed targets and lased moving targets. After release, LJDAM initially guides to a target using baseline
Global Positioning System (GPS) aided Inertial Navigation System (INS) guidance. The DSU-38/B
processes laser energy received to facilitate the acquisition of the laser pulse corresponding to the laser
code pre-selected by the laser code selection switches. If laser energy is acquired, the laser sensor provides
azimuth and elevation angle measurements to the LJDAM guidance set. The LJDAM guidance set utilizes
these angle measurements, along with estimates of the target velocity vector, to continually update the
original target coordinates provided at release. During the terminal phase, the LJDAM transitions to
proportional guidance and guides to the pre-planned or updated target coordinates, including a correction
for the target velocity, if applicable.
2
Boeing Report 15J0089
May 1, 2015
Desired
Impact Point
(Aimpoint)
• Maintain aimpoint on
target
– No leading or biasing
of aimpoint!
Initial Coordinates
Generated In
Pilot Recognizes & FLIR/POD
Designates TOO
In FLIR/POD
Target Designation
– Coordinates to LJDAM JTAC Laser Designation
Guides
Guides to
to Pre-
Pre- Laser
Laser Designation Guides
Guides to
to Laser Precision
LJDAM Release
Pre- Designation Laser Precision
Release Target
Target Detected
Detected Track
Track Coordinates
Coordinates Impact
Impact
Weapon
Baseline JDAM Optimal Angular Measurements Laser JDAM
In Free Guidance Trajectory for Between Pre-
Pre-Release Target Terminal Guidance
Flight Designated or Preplanned Coords and Detected Laser
Target Spot Used to Update Target
3
Boeing Report 15J0089
May 1, 2015
The Joint Direct Attack Munitions (JDAM) is a joint service weapon, which uses an onboard Global
Positioning System (GPS) aided Inertial Navigation System (INS) guidance set with MK 84, MK 82 and
BLU-109 warheads. The guidance set, when combined with a warhead, and appropriate fuzes, forms a
JDAM Guided Bomb Unit (GBU). The JDAM guidance set gives these bombs adverse weather capability
with improved accuracy. JDAM is capable of receiving target coordinates via preplanned mission data from
the delivery aircraft, by onboard aircraft sensors during captive carry, or from a third party source via
manual aircrew cockpit entry. After release, JDAM autonomously guides to a target, using the resident
GPS-aided INS guidance system. The JDAM weapon can be delivered from standoff ranges at high or low
altitudes against a variety of land and surface targets during the day or night.
Material applying only to the non-laser variants (GBU-31 and GBU-38 series) will be referred to as
pertaining to “baseline JDAM” while material specific to the GBU-54 will be identified as for “laser
JDAM” (or LJDAM). When “JDAM” is used without a modifier, the material applies to both variants.
Figure 1.1 shows the JDAM weapon architecture. This diagram is provided for reference only and does not
constrain JDAM design nor impose requirements.
MISSION
COMPUTER
GPS RECEIVER
TAIL ACTUATOR
SUBSYSTEM
4
Boeing Report 15J0089
May 1, 2015
1.1.1 MK 84 Configuration
The GBU-31(V)3/B consists of a BLU-109 penetrator warhead, a KMU-557B/B Guidance Set, a fuze and
fuze accessories.
1.1.3 MK 82 Configuration
5
Boeing Report 15J0089
May 1, 2015
6
Boeing Report 15J0089
May 1, 2015
MK 82/BLU-111/BLU-126/BLU-129
MK82 Warhead
KMU-572 Guidance
Kit
7
Boeing Report 15J0089
May 1, 2015
The JDAM Guidance Sets (shown in Figures 1.5, 1.6 and 1.7) consist of a Tail Assembly and a set of mid-
body or forward body aero-surfaces or “strakes”. The Tail Assembly includes the guidance electronics,
control fins, GPS Antenna, and 1760 connector. These Guidance Set components, when combined with the
appropriate fuzes, and assembled to a MK 84, BLU-109 or MK 82gravity bombs form the GBU-31, GBU-
38 and GBU-54 series Guided Bomb Units (GBU).
8
Boeing Report 15J0089
May 1, 2015
9
Boeing Report 15J0089
May 1, 2015
10
Boeing Report 15J0089
May 1, 2015
1.2.1 Strakes
The strakes are aerodynamic surfaces consisting of formed steel panels that attach to the MK 84 bomb body
to provide aerodynamic lift and maneuverability. Strakes for the BLU-109 consist of a cast aluminum
hardback and two formed steel panels. All three weapons have two strake variants currently in the field.
The older BLU-109 variants have three strake attachment straps and the current production variants have
two strake attachment straps. There are no performance differences between the above mentioned variants.
The strakes for the MK 82 consist of two formed panels that attach to the nose of the bomb body.
.
The JDAM Tail Assembly, shown in Figures 1.8 and 1.9 consists of the Tail Fairing/Structure, Tail
Actuator Subsystem (TAS), wire harness, fuze access door, umbilical cover, Guidance Control Unit
(GCU), GPS Antenna, three moveable control fins and one fixed control fin. While the tail assembly is
similar for all variants, there are some differences. On the GBU-31(V)1/B when viewing from the aft end
looking forward with the suspension lugs up, the fixed fin is located in the right hand, lower position
(Figure 1.5). The TASs for the GBU-31(V)3/B are rotated 180 from the GBU-31(V)1/B. This results in
the fixed fin location being in a different position. When viewing in the same manner, the fixed fin is
located in the left hand, upper position (Figures 1.5, 1.6 and 1.7). Additionally, the guidance software is
also unique to each configuration in order to compensate for differences in MK 84, BLU-109, and MK 82
flight characteristics. A common OFP contains guidance software that is unique to each configuration in
order to compensate for differences in flight characteristics.
11
Boeing Report 15J0089
May 1, 2015
The Tail Actuator Subsystem (TAS) consists of the aft portion of the tail assembly structure, three
electromechanical actuators to power the three movable control fins, a Lithium Thermal Battery, and the
associated controlling electronics. The aft structure provides a mounting surface for the GPS Antenna and
mounting surfaces for the control fins. The controlling electronics process digital commands into
independent fin position commands, provide fin position feedback, battery initiation, control fin unlock,
and BIT status.
The Pin Lock TAS has positive locking pins that protrude through the skin of the TAS housing into control
fin slots. The pins mechanically prevent control fin rotation during captive carriage. After release, a
solenoid unlocks a spring-actuated mechanism that retracts the locking pins, allowing control fin rotation.
Should the Pin Lock mechanism fail, the fins are restrained only by the mechanical action of the ball screw
actuator. With a Pin Lock failure, the fin is free to rotate as a function of the in-flight air loads. Pre-Flight
inspection should verify that the each fin is positively locked and will not rotate when a force is applied to
the trailing edge. When the Pin Lock TAS is powered up, a TAS BIT failure will result if control fin
rotation exceeds 1 degree during a single power on cycle (control fin rotation is not accumulated across
multiple power-on cycles). The failure code will preclude weapon employment and will invoke aircraft
specific weapon jettison envelope restrictions. Refer to the aircraft flight clearance for envelope restrictions
and safe jettison procedures with a TAS BIT failure.
12
Boeing Report 15J0089
May 1, 2015
Locking
Pins
The GCU consists of an integrated electronics assembly, which includes the mission computer, Inertial
Measurement Unit (IMU), and GPS Receiver.
The mission computer is a single board computer that contains and executes the Operational Flight
Program (OFP). Different versions of the JDAM OFP are loaded into the mission computer, depending on
the JDAM variant. The OFP is common for the baseline and laser JDAM and executes different logic if the
laser sensor is present and the laser JDAM software is commanded to be used. The mission computer
power supply conditions and supplies power to the tail assembly components from the aircraft while
captive carried and from the system thermal battery during free flight and is located on the Mission
Computer circuit card.
A three axis, strapdown, Ring Laser Gyro (RLG) IMU provides acceleration and attitude rates to the
mission computer for navigation. Acceleration and attitude rate data are integrated over time in order to
compute the weapon position and velocity data needed for navigation and guidance. Two IMU variants are
currently in the field; A-Grade and B-Grade IMUs. Grade A IMUs meet all weapon system accuracy
requirements. A-Grade and B-Grade IMUs contain common components and have common functionality;
however, some B-grade components meet relaxed INS-Only (no GPS updates) accuracy requirements.
Present JDAM production tail kits only use Grade A IMUs.
13
Boeing Report 15J0089
May 1, 2015
INS-Only accuracy is highly dependent on aircraft handoff accuracy, the specific weapon trajectory, and
weapon time of flight. Nominal weapon time of flight is generally less than the 100 second flight used to
specify JDAM INS-Only accuracy performance. Figure 1.11 illustrates the predicted impact CEP for a min-
spec IMU as a function of time of flight, assuming nominal aircraft handoff and a typical JDAM trajectory.
Predicted Unaided Impact CEP for Grade A and Grade B IMUs
45
40
30
Impact CEP (m)
25
20
15
10
0
0 10 20 30 40 50 60 70 80 90 100
A-Grade and B-Grade IMUs can be identified by part numbers. B-Grade IMU assets will have an even
dash number. A-Grade IMU assets will have an odd dash number. See the examples below:
Note: Using a Grade B IMU will not impact satellite acquisition and GPS-aided weapon system accuracy.
The JDAM GPS receiver acquires and tracks the P(Y) code signal on both the L1 and L2 GPS frequency
bands. When successfully tracking satellites, the receiver outputs Line-of-Sight (LOS) messages to the
mission computer for aiding the Inertial Navigation System (INS) solution (i.e. GPS aiding). The LOS
messages contain pseudoranges (range to satellite plus clock error times speed of light) and deltaranges
(range rate to satellite) which are processed by the JDAM Kalman filter and used to update the inertial
navigation solution. GPS crypto keys are required to allow the GPS receiver to decrypt the military
encrypted Y-code prior to measurement processing. There are currently three GPS receiver types employed
in the field; Tapestry, Nighthawk, and NavStrike. GPS functionality is similar among all three receiver
types but there are important differences summarized below.
14
Boeing Report 15J0089
May 1, 2015
The initial GPS receiver developed for JDAM was Tapestry and it is a 5-channel tracking receiver with a
Fixed Reception Pattern Antenna (FRPA). Tapestry receivers were only delivered in MK 84 tail assemblies
and can be identified by the following Part Numbers: 70P860000-1001 and 70P860000-1005.
The first GPS receiver upgrade was the 12-channel Nighthawk with a FRPA which implemented an all-in-
view tracking capability for increased accuracy over Tapestry. The additional tracking channels provide
more GPS satellite measurements for Kalman filter processing (GPS-aiding) and an improved Position
Dilution of Precision (PDOP).
The next GPS receiver upgrade was the NavStrike with Selective Availability Anti-Spoofing Module
(SAASM), which builds on the Nighthawk architecture. SAASM adds enhanced security, new GPS keying
protocols that include processing of unclassified black keys and a resistance to spoofing with the
development of a direct P(Y)-code satellite acquisition capability. NavStrike (SAASM) receivers have
excellent security and GPS keying protocols that include processing of unclassified black keys and a
resistance to spoofing with the development of a direct P(Y)-code satellite acquisition capability.
Each new generation of GPS receiver brings improved accuracy with an all-in-view tracking receiver,
enhanced tracking performance, and robustness. The JDAM OFP version delivered with Lot 9 (CY2006)
hardware also includes improvements to the JDAM Kalman filter to further improve accuracy.
The capability to use all available GPS satellite measurement data from an all-in-view 12-channel GPS
receiver was added in JDAM OFP version 2.11 and higher.
The GPS antenna receives the GPS satellite signals and feeds an RF signal directly to the GPS receiver
Fixed Reception Pattern Antenna (FRPA). The GPS Antenna is mounted on the aft face of the TAS as
depicted in Figure 1.12. The FRPA is identified by Part Number AT2775-2.
FRPA
Aft End is Flat
CRPA
Slightly Wider Than
FRPA
15
Boeing Report 15J0089
May 1, 2015
The Wire Harness consists of the umbilical connector, an umbilical connector protective cap, the FMU-152
Series Joint Programmable Fuze (JPF) connector, and a shielded harness which provides the electrical
interfaces to the GCU and the TAS.
The umbilical cover is a formed steel part that, for the MK 84 and BLU-109 variants, attaches between the
tail assembly and the hardback or upper strake. For the Mk 82 variants (including the GBU 54 LJDAM
variant) this cover/housing is physically mounted to the tail assembly. The cover positions the JDAM
umbilical connector to correctly mate with the aircraft MIL-STD-1760 interface connector and retains the
connector during separation and free flight.
JDAM is compatible with various bomb fuzes, power generators and proximity sensors. Fuze Options for
baseline JDAM are illustrated in Table 1.3 and Table 1.4 provides LJDAM fuze options.
16
Boeing Report 15J0089
May 1, 2015
The DSU-38/B Laser Kit consists of the sensor assembly, alignment pin, four strap assemblies, wire
harness, forward lower cover, mid lower cover, aft cover assembly and fuze access door assembly. The
alignment pin is utilized during installation of the DSU-38/B and is removed after buildup is complete.
The sensor assembly is installed in the forward fuze well of the MK 82 bomb body. An external wire
harness connects the sensor assembly to the LJDAM tail assembly through the fuse access door. The wire
harness is protected by the lower forward, mid and aft cover assemblies. The four strap assemblies secure
the covers and harness to the bomb body. Figure 1.13 illustrates the components provided in a DSU-38/B
kit.
When the DSU-38/B is installed, the KMU-572 JDAM Guidance Set has a Nose Extension. The Aft Strake
Strap is removed and replaced by a longer strap provided in the DSU-38/B kit. The JDAM Guidance Set
Fuze Access Door is removed and replaced with one contained in the DSU-38/B kit that provides a cut-out
to route the wire harness into the KMU-572 tail kit.
17
Boeing Report 15J0089
May 1, 2015
The sensor is cylindrical in shape with a larger diameter, hemispherical dome attached to the forward end
(see Figure 1.14). The dome section contains the laser detector assembly with optical input and laser code
selection switches. Three alignment tabs are located on the aft dome housing to aid in alignment of the
sensor with the bomb forward lug. The center alignment feature (Position 2) is used for all launch
platforms. An interface connector is located opposite the alignment tabs to connect the wire harness to the
sensor. The jam nut, located at the rear of the aft dome housing, is used to secure the sensor to the bomb
body and provide the forward longitudinal support for the strake assembly. A removable support cup is
located at the rear of the sensor. A spacer is installed on the aft end of the sensor for use with thermal
protected bombs. The sensor is protected by a friction fit protective cover with attached banding
mechanism, as shown in Figure 1.15, which is attached during shipping and handling.
Laser Code and Pulse Logic Selection: The laser code and pulse logic selection (short last or long last) are
set via panel settings on the bottom of the Sensor Assembly (see Figure 1.14). The laser code can be set
from 1111 through 1788. Set the first code switch setting to a 1L or a 1S to match mission requirements.
The update rate or laser pulse rate is fastest for the lower number codes and slowest for the higher number
codes (1111 = 20 Hertz (Hz), 1788 = <10 Hz).
3. THE PANEL SETTINGS ARE READ BY LJDAM AT WEAPON POWER ON. ANY
CHANGES MADE TO THE PANEL SETTINGS AFTER WEAPON POWER IS APPLIED
WILL NOT BE RECOGNIZED BY LJDAM UNTIL THE WEAPON POWER IS CYCLED
The Detector Assembly is a strapdown (non-gimbaled) sensor. It provides a wide linear field of view. The
Detector Assembly acquires and tracks a laser spot (or designation) and provides line-of-sight (LOS) angles
between the sensor boresight and the laser spot (or designation) in azimuth and elevation. The detector
assembly is based on a four quadrant detector (see Figure 1.16). The four quadrant detector detects the
reflected laser energy from the target and converts the photon energy impinging on the detector into
current. The relative magnitude of the energy received in each quadrant is utilized to compute the azimuth
and elevation angles.
18
Boeing Report 15J0089
May 1, 2015
A B
Laser Return
C D
19
Boeing Report 15J0089
May 1, 2015
Three protective covers, made of spring steel, are included with the DSU-38/B. The Forward Lower Cover,
Mid Lower Cover, and Aft Lower Cover Assemblies provide protection for DSU-38/B wire harness. The
forward cover is attached to the sensor with two screws at the forward end and secured by two strap
assemblies. The aft cover is secured to the KMU-572 tail assembly by two screws. The mid cover is
positioned between the forward and aft covers and secured by two strap assemblies. The forward cover has
a notch to retain and align the forward position strap assembly. A rubber spacer, located on the forward end
of the forward cover, prevents the wire harness connector screws from loosening once the forward cover is
installed. The mid cover has two notches to retain and align both the center position strap assembly and the
aft position strap assembly.
Four stainless steel strap assemblies are fastened around the bomb body. Tension for each strap is provided
by a barrel bolt and nut. The DSU-38/B Strake Strap Assembly replaces the aft aero surface strap from the
GBU-38 aero surface assembly. Forward position, center position and aft position strap assemblies are used
to secure covers around the bomb body. The cylindrical straps include a bend to contour the covers and
serve as an alignment feature. Strake strap and forward position strap assemblies secure the forward cover
to the bomb body. Center position and aft position strap assemblies secure the mid cover to the bomb body.
The DSU-38/B Fuze Access Door Assembly replaces the GBU-38 tail assembly fuze access door. When
installed, a notch in the lower right corner provides a path for routing the DSU-38/B wire harness into the
tail assembly. A lanyard and stud nut attaches the fuze access door assembly to the GBU-38 tail assembly.
The DSU-38/B Fuze Access Door Assembly provides access to the tail fuze, Joint Programmable Fuze
(JPF) or FMU-152 series fuze cable, tail assembly wire harness, and guidance control unit (GCU).
The Fuze Access Door provides access for visual inspection of fuze setting and cable connections, but the
laser wire harness may need to be pulled outside of fuze access door opening to provide clear view of fuze.
Proper re-stowage of wire harness is required to ensure weapon operation.
A Wire Harness runs along the bottom exterior surface of the bomb body opposite the launch lugs. It
includes a rectangular bayonet connector, two round right angle connectors and interconnecting wiring.
The Wire Harness connects to the DSU-38/B sensor assembly at the forward end and connects to the tail
assembly GCU at the rear through the modified fuze access door. It routes 28 volt electrical power to the
seeker assembly, which is powered by the aircraft pre-launch and by the tail kit thermal battery post-
launch. It also provides digital communication between the tail kit and the sensor assembly.
Figure 1.17 provides a depiction of the GBU-54 with the KMU-572 Guidance Kit and DSU-38/B Laser Kit
installed.
20
Boeing Report 15J0089
May 1, 2015
21
Boeing Report 15J0089
May 1, 2015
8.0 Overview
JDAM is equipped with a MIL-STD-1760 interface and is capable of employment from various aircraft
platforms. The MIL-STD-1760 interface allows the aircraft to initialize and control the JDAM and program
the FMU-152 series Joint Programmable Fuze prior to release. Power, 1553 mux and discrete data are
transferred between the host aircraft and JDAM in accordance with the JDAM Interface Control Document
(ICD) and related aircraft specific JDAM ICD Annex. The JDAM 1760 umbilical connector allows support
equipment to download software or to test the weapon. JDAM mechanically interfaces with host aircraft
suspension equipment using 30” lug spacing for 2000 lb variants (MK 84 and BLU-109) and 14” lug
spacing for the 500 lb (MK 82) variants.
JDAM is a bomb-on-coordinates (BOC) weapon, which requires the input of accurate target coordinates.
Target coordinates can be transferred to JDAM through mission planning data transfer devices (pre-planned
missions), through on-aircraft targeting systems (self-targeting), or manually through cockpit data entry
panels. In all cases, JDAM requires target coordinates in Latitude, Longitude, and altitude (Mean Sea Level
(MSL) or Height Above Ellipsoid (HAE)) referenced to a World Geodetic System (WGS)-84 coordinate
frame. JDAM navigation and guidance algorithms use HAE. If target altitude is provided as MSL, LJDAM
will convert the MSL altitude to HAE using a table with Earth Gravity Model (EGM) 84 (or EGM-96 if
selected by the aircraft) conversion values. Values in between the table values are linearly interpolated,
resulting in some conversion error. Conversion of MSL from other than WGS-84 datum may result in
additional error. If possible, target altitude should be provided to JDAM as HAE.
The above also applies to LJDAM but LJDAM adds the capability to update target coordinates to a
predicted aim point based on laser measurements. Laser energy from a ground or airborne laser designator
is used by the Sensor Assembly to measure LOS angles. The LJDAM mission computer adds functions to
maintain precise estimates of the predicted target position, enabling the terminal guidance mode to steer the
LJDAM to the laser spot. A new terminal guidance mode provides continuous guidance commands until
impact. Figure 8.1 provides a summary of LJDAM guidance.
22
Boeing Report 15J0089
May 1, 2015
Table 8.1 summarizes weapon system accuracy requirements specified by the JDAM Operational
Requirements Document and JDAM System Specification. The JDAM Weapon shall achieve the system
accuracy defined in the table that includes the contribution of GPS Quality Handoff (for INS-Only
missions) and Target Location Error (TLE) on total weapon system miss distance. For lased missions, the
System Accuracy values include a target location error of 37m (1 sigma) and a GPS quality handoff from
the launch aircraft.
When generating CAT III (or worse) coordinates, without the capability of setting the relative targeting bit
in the weapon, the GPS-aided CEP may exceed the values specified in Table 8.1. Additional detail on
Relative Targeting is provided in section 8.2.1.1.1.
JDAM and LJDAM without Laser Guidance INS-Only Accuracy Specification Requirements
(No GPS Updates Received by the JDAM Weapon After Launch)
Impact Angle
CEP Target Weapon Weapon
(Relative to Trajectory
(meters) Type Navigation Flight Time
Target Face)
On-Axis 100 sec
30 Horizontal 60 INS-Only
Off-Axis 90 sec
On-Axis 100 sec
32 Vertical 60 INS-Only
Off-Axis 90 sec
GPS-Aided Accuracy Specification Requirements
Impact Angle
CEP Target Weapon Weapon
(Relative to Trajectory
(meters) Type Navigation Flight Time
Target Face)
5 Horizontal 60 GPS-Aided All 30 sec
6 Vertical 60 GPS-Aided All 30 sec
8 Horizontal 35 and 60 GPS-Aided All 30 sec
Table 8.1 - JDAM and LJDAM without and with Laser Guidance Weapon System Accuracy
Requirements
23
Boeing Report 15J0089
May 1, 2015
24
Boeing Report 15J0089
May 1, 2015
Figures 8.2 and 8.3 graphically depict the weapon system accuracy, specified as a system CEP, for GPS-
aided and INS-Only navigation (assuming system specification GPS Quality Handoff, specification TLE,
horizontal target, and 600 impact angle).
In Figure 8.2, errors allocated to position/velocity handoff and TLE are a function of aircraft navigation
system accuracy and the accuracy of the targeting source respectively. For INS-Only missions, CEP will
increase with increased horizontal position and velocity error. CEP will also increase with increased
vertical position and velocity error and decreased impact angle. For increased TLE, CEP will increase with
increased horizontal position error and as a function of impact angle for increased vertical position error.
[Note that CEP used here is a statistical calculation derived from multiple missions which is the radius of
the circle centered at the target which contains 50% of the actual weapon impact points].
Figure 8.3 shows that accuracy is initially a function of INS-Only accuracy until JDAM acquires GPS
satellites and satisfies the GPS Loop Closure logic for GPS-aiding. Given a GPS Quality Handoff, 13 meter
CEP accuracy is available for approximately 30 seconds without GPS aiding. Once the GPS Loop Closure
completes, weapon system accuracy is only a function of TLE, guidance error and GPS-aided navigation
error. Aircraft position and velocity handoff errors are no longer a factor because the GPS updates remove
them from the weapon navigation solution.
The factors affecting LJDAM accuracy for this mode are the same as for baseline JDAM, enabling identical
accuracy against a GPS/INS targeted location. The recommendations for optimizing LJDAM accuracy are
the same as baseline JDAM. If the target is not lased, LJDAM guides to the original target coordinates
provided by the aircraft at release (adjusted to account for any valid target velocity bias handover
information), with accuracy performance identical to baseline JDAM. Due to some differences with how
LJDAM flies in the terminal phase, LJDAM impact angle performance may be slightly degraded versus
baseline JDAM. Also, for an impact angle command >= 45 degrees, the LJDAM will not collapse AOA at
impact.
25
Boeing Report 15J0089
May 1, 2015
30
25
20
CEP - meters
15
10
Position Handoff (9.6 meters)
Velocity Handoff (12.6 meters)
Guidance (1 meters)
0
0 10 20 30 40 50 60 70 80 90 100
30
25
20
CEP - meters
10
Position Handoff System (RSS) GPS-Aided 5 meters CEP
(No GPS Jamming)
26
Boeing Report 15J0089
May 1, 2015
Aircraft handoff accuracy is driven by the accuracy of the aircraft navigation system. Minimum aircraft
navigation system accuracy required by JDAM is identified by the term “GPS Quality Handoff” and is
specified as:
GPS Quality Handoff is based on expected accuracy, given the GPS Signal in Space (SIS) characteristics
circa 1994 and a properly mechanized aircraft GPS-aided navigation system operating with a low GPS
Figure of Merit (FOM).
Target Location Error (TLE) is a function of the accuracy of the targeting system. The TLE requirement,
typically guaranteed by standard mensuration sources, is specified as:
The TLE contribution to weapon miss distance for a 60 0 impact angle can be calculated to be 3.75 meters
CEP. TLE from some targeting systems may be worse than the specification requirement, which correlates
directly into larger weapon system miss distance.
The weapon guidance function attempts to steer the vehicle such that its navigated position intercepts the
transmitted target. Weapon guidance error is a measure of how close the navigated position comes to the
transmitted target in the specified target plane. For example, the guidance error for a horizontal target is
determined by computing the distance between the latitude and longitude of the weapon’s navigation
solution with the latitude and longitude of the transmitted target at the instant of time that the navigated
altitude is equal to the transmitted target altitude. The JDAM Guidance accuracy requirement is about 1
meter CEP (for a 600 impact angle).
27
Boeing Report 15J0089
May 1, 2015
A summary JDAM power-up to release timeline is shown in Figure 8.4. This figure gives the typical data
message traffic between the host aircraft and the JDAM to perform status monitoring, initialization, transfer
alignment, Mission and GPS data transfer and release.
Keys Loaded
4.1 sec CTSS:
- Battery Squib
ID: JDA M - Battery Volt. Good
Respo nds "ON"; BIT Status READY - Xfer Align Rc vd'
f16rlseq.ppt
28
Boeing Report 15J0089
May 1, 2015
JDAM mission planning is accomplished at the unit level using the JDAM Aircraft/Weapon/Electronic
(A/W/E) software application module, integrated with the current computerized mission planning system
core software functions and the host aircraft A/W/E software functions. The JDAM A/W/E provides
planners the capability to assign JDAM targets and release points to one or more weapons, enter relevant
data (such as target coordinates, release parameters and fuze data) and perform trajectory calculations to
confirm/achieve desired mission objectives. Figure 8.5 illustrates the JDAM weapon impact conditions.
Local Vertical
JDAM Velocity Vector
The JDAM A/W/E consists of a software module that provides a graphical user interface, weapon “flyout”
model, and analysis tool. Key functions include a “Target Manager” window that manages all targeting
data and a “Release Manager” window that manages weapon release points and conditions. The JDAM
A/W/E functions in an integrated manner with the host aircraft AWE via messages and data files. All
JDAM mission data, including GPS crypto keys and almanac data, is stored on the aircraft Data Transfer
Device (DTD) by the aircraft A/W/E for subsequent transfer to the host aircraft. The preplanned mission
data, GPS data, and target data, will automatically be transferred with aircraft power application, from the
DTD to the JDAM via Mass Data Transfer (MDT). The JDAM A/W/E also provides printed data for
aircrew use on board the aircraft during execution of the mission.
The JDAM weapon requires targeting data from the host aircraft to establish target location and weapon
impact parameters. Each JDAM weapon is capable of storing up to eight target data sets. Prior to weapon
release, one of the Target Data Sets (TDSs) must be selected as the target of choice. Table 8.4 provides a
list of possible data that can be included in a TDS for a single target. The parameters identified as
“required” in the TDS column constitute the minimum TDS parameters required by the JDAM weapon to
complete its mission. The “optional” data provides enhancements to the weapon operation and
performance.
The success of a JDAM mission is highly dependent on the precision of target coordinates. The JDAM
target coordinate precision provided to the mission planner should be to the ten-thousandths of an arc-
minute, or to the hundredths of an arc-second if possible. The automated JDAM mission planning
capabilities support input of the target coordinates in both of these formats.
29
Boeing Report 15J0089
May 1, 2015
An important characteristic of JDAM is that regardless of how the WGS 84 target coordinates are
generated (onboard targeting systems, JTAC, mensurated, LJDAM laser seeker), JDAM (and LJDAM) will
always guide to the set of WGS 84 target coordinates, Latitude, Longitude, and altitude, that are transmitted
to the weapon. As explained previously in this document, the target altitude reference may be one of two
MSL models or height above the ellipsoid. The accuracy of the WGS 84 target coordinates is a measure of
how close the transmitted target coordinates are to the true WGS 84 target coordinates. The difference
between the true WGS 84 target coordinates and the transmitted target coordinates is defined as Absolute
Target Location Error (TLE) in the following discussion (see Figure 8.6a).
30
Boeing Report 15J0089
May 1, 2015
True Target
Absolute TLE
Transmitted Target
When a target is designated with an onboard targeting system (pod) or ground-based designator, the
targeting system is sensing a line of site (LOS) vector or relative position vector from the pod/designator
location to the designated point on the ground. This vector is defined by the azimuth angle relative to the
pod boresight, the elevation angle relative to the pod boresight, and the range along the line of sight from
the pod to the designated point. Given a perfect relative position vector and a perfect navigated position and
attitude (yaw, pitch, and roll) of the pod, the aircraft can compute a set of WGS 84 coordinates equal to the
True Target location (see Figure 8.6b).
Unfortunately, there is no targeting system that has zero navigation error and/or perfect line-of-sight vector
measurements. Given this fact, you can expect that the computed target coordinates will have error
components corresponding to the navigation error of the targeting platform at the time of coordinate
derivation and corresponding to the targeting sensor’s line-of-sight measurement errors (azimuth, elevation,
and range errors). Therefore, when the coordinate offsets are combined with the targeting system position
at designation, the resultant WGS 84 coordinates are not exactly at the true target, but are displaced by the
navigation and measurement errors of the onboard targeting system. First, consider the case where the
aircraft navigation error is zero. The sensed target is offset from the true target only due to the sensor errors
(see Figure 8.6c).
True Aircraft Position
True LOS Vector
True Target
Sensed LOS Vector
Relative TLE
Sensed Target (due to Sensor Errors)
Now assume that the aircraft navigation error is nonzero. Since the target coordinates are computed by
adding the relative location of the target with respect to the aircraft navigated position, the Sensed Target
31
Boeing Report 15J0089
May 1, 2015
coordinates are displaced from the True Target by the sum of both the TLE due to Sensor Error and the
TLE due to Handoff Error (see Figure 8.6d).
Transmitted Target
Given these coordinates, a JDAM released in its normal GPS operating mode will remove the aircraft
handoff error from its navigation solution causing it to guide to the Transmitted Target in the above
diagram. The system miss will then be a combination of a small JDAM GPS-aided navigation error and the
Absolute TLE. The Absolute TLE will be the combination of both TLE due to Handoff Error and the
relative TLE due to Sensor Errors. If the navigation error of the targeting aircraft at designation is large,
resetting JDAM to a GPS navigation reference frame could significantly increase system miss distance
from the true target.
Since position handoff error is presumably common to both the Absolute TLE and JDAM navigation at the
time of release, handoff error can be effectively cancelled out of the final miss distance if the JDAM
precisely preserves the handoff position error throughout its flight. There are two ways to preserve the
position handoff error: (1) inhibit JDAM acquisition of GPS satellites or (2) invoke the JDAM relative
targeting mode (RT). Inhibiting GPS acquisition incurs two penalties: (1) JDAM does not have any GPS
measurements to correct for JDAM IMU drift after release and (2) any velocity handoff error will not be
corrected by GPS measurements and will be integrated over the time of flight to produce additional system
miss. Both IMU drift and velocity error will increase miss distance as a function of weapon time of flight.
However if RT is invoked, the weapon creates a biased GPS-aided solution that preserves the position
handoff error from the aircraft within 1-2 meters, CEP, throughout weapon flight. This 1-2 m error term is
defined as the weapon relative navigation error. This implies that the total system miss in the RT mode can
be reduced to approximately the Relative TLE plus the weapon relative navigation error plus the change in
aircraft position error between the time of target coordinate derivation and the time of weapon release (as
described in the following paragraph).
In order for the RT to effectively remove the position handoff error, the aircraft position error component
of Absolute TLE must be the same as the aircraft position error at weapon release. JDAM transfer
alignment is a continuous process from shortly after power up until weapon release. The transfer alignment
process will cause JDAM to have the same position error and very nearly the same velocity error as that of
the aircraft at any time after the first minute or two of transfer alignment. However, since transfer
alignment is a continual process, any time delay between target designation by an onboard sensor and
release can result in a handoff error being applied to the Transmitted Target that is different from the
handoff error imparted to the JDAM at release. This difference can be significant if the aircraft navigation
32
Boeing Report 15J0089
May 1, 2015
is degrading due to loss of aircraft GPS updates or some other navigation system anomaly. The effect of
this handoff error difference is to create another TLE error component equal to the difference between the
handoff error at designation and the handoff error at release. While the handoff error at release can be
eliminated by RT, the difference between the handoff error at designation and release cannot. The system
miss is therefore increased and the weapon will guide to a point offset by the relative TLE due to Sensor
Errors, the TLE due to Handoff Error Difference, and the weapon relative navigation error.
When LJDAM is commanded into the relative targeting mode, a bias will be applied to its GPS-aided
navigation solution to preserve the aircraft navigation position handoff error throughout the weapon’s flight
until the LJDAM begins using laser measurements, if available, to update the estimated target position and
velocity vector.
GPS crypto keys, GPS almanac data, and GPS configuration data are included as part of the JDAM mission
planning initialization data loaded on the DTD. GPS ephemeris and precise time data is downloaded from
the host aircraft GPS receiver during the mission prior to weapon release. The automated JDAM mission
planning capabilities include a GPS prediction tool that presents the mission planner with release windows
that have sufficient GPS satellite coverage for a JDAM release. The mission planner can therefore tailor
weapon release times based upon the satellite coverage provided by the GPS constellation.
JDAM implements a fast acquisition mode, which requires valid GPS Ephemeris, Almanac, Time, and
Keys to be downloaded from the host aircraft to the JDAM GPS receiver. See Section 8.2.4.1.2 for details.
33
Boeing Report 15J0089
May 1, 2015
Locking
Pins
No Free Rotation
34
Boeing Report 15J0089
May 1, 2015
Weapon operation is described as a series of weapon "states" starting with the Off state (no electrical power
applied), and proceeding through the other captive carriage states to weapon launch (Launch state) and the
transition to free flight (Free Flight state). The weapon states are not requirements but are intended as a
convenient medium for discussing required weapon functions. A detailed description of the weapon
“states” is provided below:
Off State
The Off State is unpowered captive-carriage, with no communication between the aircraft
and the JDAM weapon.
Initialization State
JDAM initialization starts with application of 28 VDC #1 power by the aircraft. Within
0.5 sec after power application JDAM will respond “on” with a message on the data bus.
If commanded, an Initiated Built-in-Test (IBIT) is completed and the results are reported
back to the aircraft. LJDAM will always command an IBIT, including IBIT of the DSU-
38/B sensor assembly, upon application of power. Initialization and mission data are
transmitted to the weapon and status messages are reported back to the aircraft.
Initialization includes a fixed 2.5 minute warm-up process that insures the weapon
electronics are properly warmed up before transfer alignment (TXA) is initiated. After
warm-up is complete and the weapon has received the minimum TXA data set, TXA
begins.
Initiated BIT (IBIT) may be commanded by the aircrew anytime after power application.
IBIT consists of a comprehensive series of weapon tests designed to determine the ability
of the weapon to perform its mission. IBIT will halt the ongoing transfer alignment
process. The alignment process will automatically be continued upon completion of IBIT.
IBIT will have no impact on previously loaded GPS initialization data (i.e. Almanac and
Ephemeris Data), GPS Crypto Keys, and Target Data Sets. When IBIT is commanded the
weapon will interrupt normal operation and will complete IBIT within 20 seconds. IBIT
of the DSU-38/B sensor assembly is within the timeline of the JDAM IBIT. IBIT cannot
be activated during the Launch Sequence.
35
Boeing Report 15J0089
May 1, 2015
and can verify that JDAM is operating on battery power by checking for CTSS at least 80
msec after aircraft power removal. The aircraft then completes the launch state by
initiating an aircraft specific launch sequence that separates the weapon from the aircraft.
Minimum time for release is about 900 msec but can be longer due to aircraft specific
launch sequence timing. The launch state can only be entered from the AUR Ready State,
or Initialization State with Safe to Release. However, if Launch State is entered from the
Initialization State, the weapon may not meet performance specifications.
Abort State
The Abort State is a state the JDAM enters as a result of any aircraft or weapon event that
aborts the weapon timeline processing. Abort may be entered from the Initialization
State, AUR Ready State, or the Launch State, upon aircraft command or autonomously
when the JDAM detects a safety critical failure. The aircraft determines the need to abort
the timeline by monitoring critical functions of the following categories:
JDAM BIT
Host aircraft detecting improper or lack of JDAM response
Host aircraft detecting a store station failure or a hung store
Host aircraft detecting any safety critical conditions or failures
For fighter aircraft that carry the weapon externally, in flight above 1000 feet MSL, the JDAM has no
power on time limit. Below 1000 feet MSL, at an ambient temperature of 113 F, power on time should be
restricted to 45 minutes to prevent over heating of the JDAM guidance set components.
A summary JDAM power-up to release timeline is shown earlier in the document in Figure 8.4. This figure
gives the typical data message traffic between the host aircraft and the JDAM to perform status monitoring,
initialization, transfer alignment, Mission and GPS data transfer and release.
JDAM and LJDAM provide a comprehensive set of status indications to the aircraft to indicate state of
readiness for launch. Figure 8.9 summarizes these status indicators.
36
Boeing Report 15J0089
May 1, 2015
During initialization, the LJDAM shall execute a BIT on the DSU-38/B sensor and periodically thereafter
while power is applied. The initial BIT of the DSU-38/B sensor is within the timeline of the normal JDAM
system initial bit. BIT failure of the DSU-38/B laser sensor is not classified as a critical hardware failure
since baseline JDAM performance is available without laser capability. An LJDAM sensor BIT failure will
result in AUR Not Ready, Last BIT Passed set to Fail and Laser Sensor BIT set to Fail. Monitoring and
cockpit display of the LJDAM status indicators are aircraft specific. The aircraft specific -34 manual should
define what is monitored and the interpretation of cockpit displays
Safe to Release provides the lowest state of readiness for launch. Launching with only Safe to Release
conditions met may not support desired weapon system accuracy.
Weapon launch with Safe to Release will meet INS-Only (no GPS updates) performance, when
o NAV Quality set GOOD, Min GPS Data set false, no BIT failures, and aircraft provides a
GPS-Quality handoff at release
Weapon launch with Safe to Release will meet GPS-aided performance, when
o NAV Quality set MARG, and no BIT failures
o NAV Quality set GOOD, Min GPS Data set true, and no BIT failures (Note: these
conditions will set AUR Ready true)
Weapon launch with Safe to Release will produce unpredictable results, when
o NAV Quality set UNSAT or MARG, and Min GPS Data set false or GPS receiver BIT
fail
Lack of valid Ephemeris, time or valid GPS crypto keys will be indicated by the weapon status word Min
GPS Data not received which should produce an aircraft specific Degraded Mode indication in the cockpit.
Min GPS Data not received means GPS-aiding will not be available (degraded mode).
37
Boeing Report 15J0089
May 1, 2015
AUR Ready is the highest state of readiness for launch and means all required initialization data has been
received, there are no hardware failures detected by PBIT/IBIT, and transfer alignment has progressed to a
Good state. Launch under these conditions will support GPS-aided performance, INS-only performance,
and Lasing mode performance and provides the highest probability of achieving specification accuracy
requirements and meeting mission objectives.
The availability of JDAM status indicators to the aircrew is aircraft specific. Refer to the aircraft specific
ICD Annex and –34 to determine what status indicators are available to the aircrew and how they are
displayed.
The purpose of Transfer Alignment (TXA) is to align the JDAM IMU to the aircraft IMU. The process
involves a transfer of information from the high quality aircraft Inertial Navigation System (INS) to the
lower quality, lower cost weapon INS. The transfer of position and velocity information requires only a
means of communicating data to the weapon and knowledge of the location of the weapon INS relative to
the aircraft INS. The transfer of alignment, which is the transfer of attitude or angular information, is not
as easy. It is not practical to precisely orient the weapon on the aircraft during loading and there will be
relative movement in any case during flight due to flexure and vibration. An angular misalignment of one
degree is a monumental error for the purposes of navigation.
Indirect means are used to accomplish the transfer of alignment data. The theory behind the transfer
alignment process is that if two inertial systems, in this case the aircraft and weapon INS, are subjected to
the same input accelerations and rates, then their outputs should be identical. The aircraft INS is assumed
to be perfect and the weapon INS is forced to have a matching output. This is usually accomplished by
comparing the output velocities or velocity integrals of the two inertial systems. The difference in velocities
or integrated velocities is the input to the weapon Kalman filter that estimates the weapon INS attitude
errors and corrects the navigation solution. JDAM or LJDAM TXA should not be initiated (by power up)
until the aircraft navigation system has reached an accurate state. Initiating TXA while aircraft INS
alignment is still in progress may cause JDAM Kalman filter states to reach incorrect values that will
impede normal TXA progression.
A useful by-product of the TXA process is the estimation of some weapon INS sensor errors such as
accelerometer bias, accelerometer scale factor error, and gyro drift rate. These errors can be compensated
so the weapon INS actually undergoes a dynamic calibration during the last few minutes before the weapon
is launched. Some error sources are observable during straight and level aircraft flight. Others require that
the aircraft perform a maneuver (a transfer alignment maneuver (TAL)) so the sensor errors can be
observed and corrected. The TAL maneuver usually consists of a series of aircraft heading changes, but the
exact form is not important, just that the velocity changes in magnitude or direction. A 30º bank for a 30-
degree heading change is usually very effective. A typical transfer alignment maneuver for a fighter aircraft
is shown in Figure 8.10. A typical transfer alignment maneuver for a bomber aircraft is shown in Figure
8.11.
JDAM or LJDAM TXA should not be initiated (by power up) until the aircraft navigation system has
reached an accurate state. Initiating TXA while aircraft INS alignment is still in progress may cause JDAM
Kalman filter states to reach incorrect values that will impede normal TXA progression.
38
Boeing Report 15J0089
May 1, 2015
2-3 G Turn
Figure 8.10 - Typical Fighter Transfer Alignment Maneuver
Nav Quality overrides will take effect when abnormally large estimates of JDAM IMU instrument errors
are detected. These overrides are important to detect off-nominal performance caused by either poor quality
alignment data from the aircraft or a JDAM IMU malfunction. IMU instrument errors are detected and
corrected in the JDAM Kalman filter by adjusting gyro and accelerometer bias states to match JDAM
measured velocity (or velocity integral) data to the equivalent aircraft IMU data. First and second tier bias
state thresholds are established based on nominal IMU instrument error characteristics. If a bias state
exceeds a first tier threshold for a minimum of 20 seconds, the Nav Quality will be limited to no better than
MARG (Marginal). If a second tier threshold is exceeded, the Nav Quality will be forced to UNSAT
(Unsatisfactory). The thresholds for these overrides are computed as a function of altitude. At high
altitudes, the thresholds relate to 3 sigma IMU instrument error expectations for MARG and 5 sigma IMU
instrument error expectations for UNSAT. At lower altitudes, the thresholds are relaxed somewhat since
JDAM flight times will be shorter, limiting unaided navigation drift. A weapon power cycle will initiate a
new transfer alignment and will clear the Nav Quality overrides. In addition, JDAM Block 08 software
(Oxx391) and later relaxes the NSQ override thresholds for gyro bias estimates beyond 3 and 5 sigma
expectations after more than 5 minutes of transfer alignment have completed . This change was included to
eliminate nuisance NSQ overrides for a relatively small population of JDAM IMUs whose gyro biases have
shifted since initial delivery. INS-only performance of these units with large gyro biases is not negatively
impacted once sufficient transfer alignment has been conducted to allow the weapon to estimate the gyro
bias.
JDAM and LJDAM provide to the aircraft, via the 1760 interface, two status words that indicate the state of
transfer alignment (TXA). Availability of these indicators to the aircrew is aircraft specific.
TXA Quality: The first weapon status word, TXA Quality, is an indication of the current uncertainty of the
JDAM attitude. The numerical value represents the square root of the sum of the squares (RSS) of the level
tilt and azimuth uncertainties from the weapon’s Kalman Filter, expressed in milliradians. TXA Quality has
an integer value between 01 and 10, with 01 indicating the best TXA Quality. Level tilt uncertainties
collapse relatively quickly after the start of transfer alignment measurements, but azimuth uncertainty
remains large until aircraft maneuvers provide sufficient horizontal acceleration to make azimuth error
39
Boeing Report 15J0089
May 1, 2015
observable. Hence, TXA Quality serves as a Transfer Alignment (TAL) maneuver desired indication to the
pilot. If TXA Quality is greater than 01, then JDAM unaided navigation accuracy would be improved by a
TXA maneuver. If TXA Quality is not improved to 01 following a TXA maneuver, JDAM performance
shall meet the JDAM GPS-aided accuracy requirement.
NAV Quality: The second weapon status word, Navigation Solution Quality (NAV Quality) is an overall
indication of whether JDAM is capable of meeting weapon system specification accuracy requirements.
For the LJDAM, Navigation Solution Quality (NAV Quality) is an overall indication of whether LJDAM is
capable of meeting JDAM system specification accuracy requirements when operating without LASER
guidance. The NAV Quality indicator has values of UNSAT (Unsatisfactory), MARG (Marginal), and
GOOD.
UNSAT implies that JDAM may not meet either GPS-aided or INS-Only accuracy specification
requirements (GPS acquisition may not succeed)
MARG indicates that the JDAM shall meet its GPS-aided accuracy requirements
o Provided weapon flight time is sufficient (>32 seconds)
GOOD indicates that the JDAM shall meet its INS-Only accuracy requirements
MARG will be indicated when the RSS of the JDAM level tilt uncertainties (azimuth uncertainty not
included) falls below 1.5 milliradians. This will typically occur within 30-60 seconds of the start of transfer
alignment, even in the absence of an alignment maneuver. When MARG is displayed, the JDAM has
achieved sufficient NAV Quality to support GPS-aided accuracy, provided that the weapon flight time is
sufficient (>32 seconds) and acquisition is not inhibited by GPS jamming. Note that MARG will only be
displayed if the JDAM GPS subsystem is healthy and all data required for JDAM GPS acquisition has been
provided by the aircraft. If NAV Quality is not improved from MARG to GOOD following a TXA
maneuver, JDAM performance shall meet the JDAM GPS-aided accuracy requirement. Repeated TXA
maneuvers are not required.
GOOD is indicated about one (1) minute after TXA Quality reaches 01. This one minute delay allows for
Kalman Filter settling time. The delay is accomplished by passing the composite tilt uncertainty (the RSS
of the level and azimuth tilt uncertainties) through a first order filter. NAV Quality will transition to
GOOD when the filtered composite tilt uncertainty (includes both level tilt and azimuth uncertainty)
decreases below 1.5 milliradians. NAV Quality will transition from GOOD back to MARG (or UNSAT if
the GPS subsystem is unhealthy) with 1) the unfiltered composite tilt uncertainty increases above 1.5
milliradians and the duration of the GOOD indication has exceeded three minutes, or 2) the unfiltered
composite tilt uncertainty increases above 2.5 milliradians.
NAV Quality overrides will take effect when abnormally large estimates of JDAM IMU instrument errors
are detected. These overrides are important to detect off-nominal performance caused by either poor quality
alignment data from the aircraft or a JDAM IMU malfunction.
8.2.3.5.1 Nominal TXA Quality and NAV Quality Timeline from Weapon Power-On
At power-on, TXA Quality and NAV Quality will be initialized to 10 and Unsatisfactory, respectively
[10/UNSAT]. A TXA progression starts after warm-up is complete (2.5 minutes after weapon power-up)
and receipt of TXA initialization messages that contain moment arm (accounts for physical displacement of
each weapon station from aircraft INS reference point) and TXA interval data. Following successful
transmission of that data, TXA commences with the first valid Periodic Transfer Alignment Message
(PTAM) sent from the aircraft to JDAM and continues at the established TXA interval up to weapon
release. The PTAM message contains time stamped attitude, position, velocity/velocity integral and time
data. The PTAM data is input to the JDAM TXA filter in parallel with equivalent measured data from the
JDAM IMU. The filter compares the two data sets and updates error state estimates as well as a covariance
matrix that describes the 1-sigma uncertainty of each error state and its correlation with other error states.
Level attitude (roll/pitch) errors are very observable and will be determined within a milliradian after 30-60
40
Boeing Report 15J0089
May 1, 2015
seconds of TXA measurement processing (3-3.5 minutes after weapon power on). At this time, the NAV
Quality indicator will change to Marginal [10/MARG] provided that the JDAM GPS subsystem passes BIT
and all required GPS initialization data has been received by the JDAM. Azimuth attitude error is not
observable until a horizontal acceleration of sufficient magnitude and duration is provided via a TAL
maneuver. After the TAL maneuver is initiated, the azimuth error is estimated, causing the “z” attitude
error covariance, and hence the TXA Quality indicator to decrease from 10 to 1 [01/MARG]. After TXA
Quality reaches 01, an additional period of 30-60 seconds is required for the JDAM Kalman filter to
converge, resulting in JDAM reporting Good [01/GOOD]. Then, after a prolonged period of straight and
level, non-accelerating flight, the azimuth error will begin to increase causing the TXA Quality to begin
counting up, and the NAV Quality to transition to Marginal [e.g. 3 or higher/MARG] (GPS healthy) or
UNSAT (GPS not healthy). A subsequent TXA maneuver will then quickly reestablish a TXA Quality of
01 and a NAV Quality of GOOD. If a NAV Quality of GOOD is not obtained within 60 seconds of
achieving TXA Quality of 1, it is an indication that a NAV Quality Override has occurred.
Situational awareness of TXA state depends upon what the aircraft displays to the aircrew. If the aircrew
can monitor both TXA Quality and NAV Quality, releasing JDAM with a 01/GOOD is preferable for both
the GPS-aided and INS-Only free flight cases. If only NAV Quality is displayed, release with GOOD is
preferable. This will ensure the best possible JDAM CEP performance is achieved.
A JDAM can be launched with a NAV Quality of MARG and achieve expected JDAM GPS-aided
accuracy, provided that GPS-aided navigation is expected. Hence, aircrew may choose to release a JDAM
with a Nav Quality of MARG if the expected time of flight is greater than 32 seconds and no problems are
indicated in the JDAM GPS subsystem (JDAM GPS Fail, No Crypto Keys, Almanac, Ephemeris and/or
time missing or invalid). For a GPS denied environment, a 01/GOOD or GOOD is required to ensure
optimum INS-Only CEP performance. CEP performance will be unpredictable if JDAM is launched with a
MARG state in a GPS denied environment.
For an UNSAT state, neither GPS-aided nor INS-Only performance can be expected. An UNSAT state
may not support GPS-aided flight because JDAM may not have the data accuracy required to achieve the
GPS fast acquisition mode. When fast acquisition is not available, the weapon will impact the ground
before GPS acquisition is complete. For the INS-Only case, an UNSAT state will increase TXA errors,
which will substantially increase miss distance. In either case, launching JDAM in an UNSAT state will
produce unpredictable results. Hence, a JDAM should not be released with an UNSAT transfer alignment
indication.
Grade B IMUs should not result in a higher incidence of NAV Quality Overrides, should not exhibit
degraded transfer alignment and the weapon should respond to TAL maneuvers. There should be no
noticeable difference to the aircrew when using Grade B IMUs.
When NAV Quality is set to MARG, it is an indication that the weapon has been properly initialized with
GPS data and has sufficient navigation accuracy to successfully acquire GPS satellites after launch (deploy
if GPS-aiding is expected after weapon release). Note that when NAV Quality is set to MARG, INS-Only
weapon accuracy may be degraded.
JDAM navigation accuracy is specified for two navigation modes; the primary navigation mode, GPS-
aided, and the backup navigation mode, INS-Only.
41
Boeing Report 15J0089
May 1, 2015
INS-Only means GPS aiding data is not available (no GPS measurement updates). JDAM INS-Only
navigation accuracy is a function of aircraft handoff accuracy, target location error, and IMU drift rate
during weapon guidance to the target. IMU drift rate is a function of how well the IMU was calibrated
during the aircraft transfer alignment process. INS-Only missions can occur during short weapon times of
flight (insufficient time to acquire and track GPS satellites) or when operating in a GPS-denied
environment (i.e. GPS jamming environment) and GPS satellite acquisition is unsuccessful.
GPS-aided navigation means that the JDAM navigation has been updated with highly accurate GPS-aiding
data. JDAM GPS-aided navigation accuracy is a function of target location error and GPS error during
weapon guidance to the target. After weapon launch, the GPS receiver quickly acquires and tracks
satellites. Once the GPS receiver is in track mode, the receiver provides satellite line-of-sight (LOS)
measurement data for GPS-aiding. The LOS data provides highly accurate position and velocity GPS
measurement data to the JDAM Kalman filter for measurement processing. The Kalman filter corrections
are used to update the navigation solution to provide GPS-aided accuracy.
The aircraft must provide GPS initialization data to the weapon to ensure a “fast” satellite acquisition after
launch. Weapon GPS initialization data requires the aircraft to provide valid ephemeris data, GPS crypto
keys, accurate time, and almanac data. The weapon will report a ‘Min GPS Data’ status of true after the
GPS receiver has been properly initialized. Additional information on initialization data is provided below:
Ephemeris data is provided from the host aircraft for the satellites tracked by the aircraft GPS
receiver and is used for precise satellite orbital position calculations
Almanac data is used by the JDAM GPS receiver to search for satellites for which it does not have
ephemeris data.
To ensure the best possible GPS-Aided navigation accuracy, valid almanac data, current within
two weeks of the mission, should be provided.
Time of day must be accurate to within 10 msec to ensure GPS satellite acquisition. In addition,
the aircraft must provide the correct month, day, and year in order to validate the time affectivity
of the ephemeris data and to validate GPS crypto keys. Inaccurate date and time will result in a
degraded weapon capability. A grossly incorrect time can cause the Ephemeris and/or the GPS
keys to be declared invalid and a weapon power cycle may be required to correct the degrade
condition even if correct time is eventually provided.
Weekly GPS Crypto Keys are provided from the aircraft or directly from the DTC. Weekly keys
are valid for a single week from Sunday to Saturday. Missions planned for the Saturday to
Sunday rollover period will require two sets of weekly keys, current week and the next week to be
loaded. Weekly keys are decoded in the JDAM GPS receiver and converted to the daily keys
required for satellite signal processing. GPS Crypto Keys may be provided as red keys for all
JDAM GPS receivers or as black keys for SAASM JDAM GPS receivers.
Complementary Navigation Messages (CNMs) are provided from the aircraft to validate the black
GPS crypto keys. Inaccurate CNM will result in degraded weapon capability.
Bad almanac (defined as almanac data that is incorrect, either because the data has been corrupted, or the
Almanac Reference (GPS) Week Number provided was not the full 16 bit value, or the data transmitted to
the weapon did not follow the required protocol) or outdated almanac (defined as almanac that was valid at
some time in the past), may result in decreased GPS-Aided accuracy. With bad Almanac, Nighthawk
receivers may incorrectly compute satellite positions when prioritizing satellites for acquisition, resulting in
acquisition attempts on non-visible satellites in place of visible satellites with ephemeris data. NavStrike
(SAASM) GPS receivers contain revised software that will prioritize acquisition of satellites with
ephemeris data over those with only almanac data, mitigating the known mechanism by which incorrect
42
Boeing Report 15J0089
May 1, 2015
almanac data degrades performance. However, this software mitigation should not be relied upon as a
substitute for providing proper almanac data.
Lack of valid Ephemeris (minimum of 4 satellites), GPS crypto keys, or time will result in the weapon
reporting a Min GPS Data status of false, which should produce an aircraft specific Degraded Mode
indication in the cockpit.
The time needed to acquire and track GPS satellites and process the GPS measurement data for updating
the navigation solution is depicted in Figure 8.11 as a function of JDAM GPS receiver type. The figure
identifies the major events that take place during GPS satellite acquisition and the incorporation of the GPS
measurements into the JDAM navigation solution. Note that GPS acquisition and track only occurs after
weapon release from the host aircraft after a finite period of time.
The Nighthawk GPS receiver timeline is shown in the top of the figure and the NavStrike GPS receiver
timeline is shown in the bottom half. The time to first fix (TTFF) for the first valid navigation update is
specified as a maximum of 27 seconds after release. GPS Loop Closure is also depicted in the figure and is
the time when GPS updates are actually applied to the JDAM navigation solution and GPS-aiding begins.
GPS Loop Closure typically occurs several seconds after TTFF after certain criteria have been met. One
criterion needed for loop closure is having good satellite geometry, small Position Dilution of Precision
(PDOP) value, to ensure the best weapon system accuracy.
Figure 8.11 - Nominal Satellite Acquisition Timeline for JDAM GPS Receivers
Satellite acquisition starts 4 seconds after release to allow the weapon to clear the aircraft. JDAM selects a
single (banked) satellite for initial acquisition. The banked satellite is the satellite closest to the GPS
antenna boresight which would also have the highest antenna gain.
43
Boeing Report 15J0089
May 1, 2015
For Nighthawk GPS receivers, initial satellite acquisition is commanded using C/A code on L1. To support
a “fast” acquisition mode, all of the correlators in the receiver (12 channels) attempt to acquire the banked
satellite independently by allocating each channel a portion of the 10 msec time uncertainty. Acquisition
of the banked satellite allows the GPS receiver to rapidly obtain the Handover Word (HOW) which
contains a truncated Time-of-Week (TOW) count to facilitate transition from C/A code to P(Y) code track.
Once the HOW is downloaded, the GPS receiver commands each individual channel to acquire and track
all visible satellites using P(Y) code on L1. Recent flight test with the Nighthawk GPS receiver indicates a
TTFF of 21-23 seconds after release can be expected, as depicted in Figure 8.11.
For NavStrike (SAASM) GPS receivers, initial satellite acquisition of one (banked) satellite is commanded
using direct P(Y) code on L1. Once the banked satellite is acquired and time is precisely known, the GPS
receiver commands each individual channel to acquire and track all visible satellites using P(Y) code on
L1. Recent flight test with NavStrike (SAASM) GPS receivers indicate a TTFF of 15-17 seconds after
release can be expected, as depicted in Figure 8.11. The 15-17 second TTFF times assumes the clock
(crystal oscillator) has been calibrated in the last five years since production. After five years, clock aging
will result in extended NavStrike TTFF times which will approach the specified requirement of 27 seconds.
Each GPS receiver type uses different GPS frequency (L1 and L2) switching logic when tracking satellites.
All weapon configurations must track GPS on both frequencies in order to accurately estimate and remove
the ionospheric delay from GPS Line-of-Sight measurement data.
Pre-Block 9 OFPs select the banked satellite as the one closest to the boresight of the antenna using the L1
frequency in these OFPs, frequency switching is based on fixed time intervals independent of the GPS
jamming environment. For weapon configurations using a NavStrike (SAASM) GPS receiver with either a
FPRA, the frequency switching logic is as follows:
Note: Current production weapons use a 12 channel GPS receiver to allow for all-in-view tracking
capability to ensure good satellite geometry. Channel 12 is dedicated to measuring noise power only and is
not used to track GPS satellites.
GPS-aiding and GPS Loop Closure occurs when a pre-determined set of criteria are satisfied and occurs
when the accumulated GPS corrections from the Kalman Filter are applied to the JDAM navigation
solution. After GPS Loop Closure, subsequent GPS corrections are applied on a real-time basis for the
remainder of the mission. The loop closure criteria ensure that the GPS-aided navigation solution will meet
weapon system GPS-aided accuracy specifications.
GPS Loop Closure requirements are dependent on the NAV Quality and GPS-aiding mode of operation.
First, a PDOP threshold value is calculated based on the NAV Quality as follows:
GPS Loop Closure occurs when at least three measurement updates have been processed with a PDOP ≤
the PDOP Threshold, and either one measurement cycle (nominally one second) has elapsed since the
weapon has processed dual frequency GPS measurements for at least 4 satellites, or the time from weapon
44
Boeing Report 15J0089
May 1, 2015
release is at least twenty-seven (27) seconds. Dual frequency GPS measurements are when measurements
from both the L1 and L2 frequencies have been processed by the Kalman filter in order to estimate the
ionospheric delay to a specific satellite. Allowing GPS Loop Closure twenty-seven seconds after weapon
release (without dual frequency GPS measurements but with good PDOP) is presumed to be more accurate
than INS-Only guidance to the target.
Baseline JDAM is capable of release at level, dive, and loft flight path angles. Releases may be executed at
flight path angles from minus 45 to plus 45 degrees. The JDAM guidance law will command the optimum
trajectory from the release point to obtain the planned impact conditions at the target. JDAM provides the
capability to deliver multiple weapons onto a single horizontal target aim-point. The guidance set can
control the terminal trajectories of the JDAM weapons to achieve impact angles of 60 degrees and greater
(relative to horizontal or vertical target plane) with a total inertial angle of attack of less than 2 degrees at
impact.
LJDAM, employed as a laser weapon, is generally restricted to level release (flight path angle of -5 to +5
degrees), however, Rule-of-Thumb tables are provided for 20, 30 and 45 degree dive cases.
The baseline JDAM weapons possess large operational envelopes in order to adapt to a wide variety of host
aircraft platforms and operational scenarios. Since the carriage, release and jettison envelopes are limited
by the individual aircraft operational platforms, these capabilities are identified in the specific aircraft
weapon delivery technical manuals. Aircraft carriage, jettison and employment envelopes are in accordance
with aircraft specific flight clearances. Note that the minimum employment airspeed at maximum
employment altitude are also a function of the fuze and fuze power source.
LJDAM, employed as a laser weapon, is more restricted in the release speed and altitude as shown in the
table below.
The JDAM munitions are capable of captive carriage, jettison and employment as presented in Table 8.5.
Carriage/Jettison
Airspeed Carriage: 0 to 650 KCAS or 1.4 Mach (0.9/50,000’ MSL)
Jettison: 0 to 1.3 Mach
Altitude 0’ AGL to 45,000’ MSL
Load Limits -2.0 to 6.0 G symmetrical
-1.0 to 4.8 G asymmetrical
Employment
Airspeed 165 to 650 KCAS or 1.3 Mach (0.9/50,000’ MSL)
LJDAM employed as a laser weapon: 0.75 to 0.95 Mach
Altitude 200’ MSL (loft release) to 45,000’ MSL
LJDAM employed as a laser weapon: HAT of 10 kft to 35 kft
Load Limits +0.5 to +6 G
Loft/Dive Angle -45 to +45 degrees
LJDAM employed as a laser weapon: -5 to +5 degrees
45
Boeing Report 15J0089
May 1, 2015
JDAM lift and maneuverability is augmented by the strakes. Total range and maneuvering performance is
a function of the kinetic energy (mass and velocity) and potential energy (altitude) at release. JDAM
guidance uses an optimal flight path from release to a final impact vector defined by the commanded
impact angle and impact azimuth projected from the target coordinates. JDAM guidance does not
specifically control impact velocity but will optimally trade off available energy to arrive at the target point
along the planned impact vector with the highest velocity possible. If sufficient energy is not available to
reach the target along the planned impact vector, the guidance algorithm will trade off the impact vector to
reach the target. Figure 8.12 shows a notional flight profile of a JDAM weapon for an off-axis mission.
Figures 8.13 and 8.14 show examples of JDAM trajectories computed as a function of impact and release
angle. The guidance algorithm provides the ability to achieve steep and shallow impacts over large
footprint areas.
46
Boeing Report 15J0089
May 1, 2015
10K
5K
-150
-300
-450
10K
The free flight state of the JDAM involves separation from the aircraft, fuze arming, GPS satellite
acquisition, optimal guidance, terminal guidance for LJDAM, and target impact. The free flight state begins
at the successful completion of the launch state. JDAM free flight profiles for a vertical and horizontal
target profile are shown in Figures 8.15 and 8.16. A laser mission flight profile is shown in Figure 8.17.
Each figure includes a “notional” GPS acquisition taking place in parallel with Optimal Guidance flight.
The weapon has a default fin unlock time of 0.3 seconds for GBU-38 and GBU-54. The unlock time can
be changed by the aircraft if the capability is implemented in the aircraft software.
47
Boeing Report 15J0089
May 1, 2015
Umbilical
Separation
Altitude INS-Only GPS-Aided
Navigation Navigation
Impact
Phase
Separation
Phase
Optimal Guidance Phase
t=0 t = Varies t=4 t = 16-24 t = 0.6 to Go
•Release •Unlock •Initiate GPS •First GPS •Drive Angle
Fins Acquisition Navigation of Attack
•Initiate Capture Update Toward Zero
and Guidance
Time (seconds)
Roll Over
Pull Down
Umbilical
Separation
Altitude
INS -Only GPS -Aided
Navigation Navigation
Separation Impact
Phase Optimal Guidance Phase Phase
48
Boeing Report 15J0089
May 1, 2015
LJDAM Senses
Laser Pulses
Umbilical
Umbilical
Separation
Separation
Baseline JDAM guidance has three modes. They are Separation, Optimal Guidance and Impact. The
LJDAM guidance has four modes – Separation, Optimal Guidance, Terminal Guidance and Impact. The
Separation, Optimal Guidance and Impact Modes are the same as for baseline JDAM, except as specified
herein. For both weapons, the separation phase starts at weapon umbilical separation. In the separation
phase, the control fins are locked and the weapon is subject to the local flow field for the specific aircraft
and release conditions. At the start of fin unlock the guidance enters the Optimal Guidance mode. In
Optimal Guidance, the guidance algorithm continually updates the flight path and issues normal
acceleration, directional acceleration and bank error commands to the autopilot. During this phase, the
baseline JDAM will maneuver as required to intercept the target along the specified impact vector. At 0.6
seconds time-to-go, the guidance transitions to Impact Mode during which Alpha and Beta are actively
controlled to achieve a total inertial AOA at impact of less than 5°. Prior to Impact Mode, the laser JDAM
transitions from optimal to proportional guidance and begins using laser measurements, if available.
LJDAM only enters Impact Mode under certain conditions as discussed below.
Separation Mode:
JDAM is released with the fins locked to prevent any control movement that could jeopardize safe
separation from the host aircraft. After the fins are unlocked, the JDAM autopilot provides fin commands
to capture angular rates, AOA and roll attitude for initial flight (see flight characteristics discussion above).
The initial flight attitude for the GBU-31(V)1B is a “+” configuration with the fixed fin down. For the
GBU-31(V)3B the initial flight attitude is an “X” configuration with the fixed fin up and to the left.
The time to the start of fin unlock varies for different JDAM variants. Also, the aircraft (if implemented in
their software) has the option to control this time via the 1760 interface.)
The default duration of the Separation Guidance Mode is 0.3 seconds for GBU-54 LJDAM, after which
time the Guidance Mode transitions to Optimal Guidance. After an additional 0.15 second delay, the
LJDAM autopilot begins the capture sequence.
49
Boeing Report 15J0089
May 1, 2015
The optimal guidance phase commences at the completion of the separation phase and continues until the
start of the impact phase, which is the last 600 msec before impact. The Optimal Guidance Law adaptively
computes, in real time, the minimal control effort (maneuvers) to go from the present position and velocity
state to the target, to achieve an impact vector at the planned impact point, based on the commanded impact
angle and impact azimuth. If all planned impact conditions are not achievable, the guidance law
compromises impact velocity first, then impact angle/azimuth, and lastly impact point.
For on-axis vertical targets, the weapon will generally (except for shorter range on-axis cases) fly in the
normal flight attitude in a gradual descent. For on-axis horizontal targets, the weapon will generally
(except for shorter range on-axis cases) fly in the normal flight attitude to some point, then roll 180 degrees
and pull down on the target. For off-axis and shorter range cases, JDAM may execute an initial turn away
from the target and then, at the appropriate point, maneuver to intercept the target.
LJDAM Optimal Guidance is modified from baseline JDAM to provide a more favorable view of the target
by the Laser Sensor (see Figure 8.31 for a comparison to baseline JDAM).
During the Terminal Guidance Mode, LJDAM transitions from optimal to proportional guidance and
begins using laser measurements, if available, to update the estimated target position and velocity vector.
Impact Mode:
The Impact Mode is the last 600 msec of flight, during which baseline JDAM collapses the total inertial
angle of attack to zero. This is done to align the warhead longitudinal axis to the velocity vector to prevent
warhead breakup. The impact phase can look like an abrupt maneuver just before impact; however, it is
normal weapon operation.
For LJDAM, only for vertical targets (commanded impact angle <45°) will the guidance transition to
Impact Mode at 0.6 sec to go. The pitch and yaw body axis angles are collapsed to align with the weapon’s
velocity vector to achieve a total inertial AOA at impact of less than 2°. For horizontal targets
(commanded impact angle >45°), Impact mode is deferred, permitting the weapon to use whatever AOA is
required to intercept the target. (Note: LJDAM provides the capability to use Impact mode for horizontal
fixed targets, but it requires that the aircraft OFP have the capability to command Target Known Stationary
(TKS) which can be done via the full laser interface).
JDAM implements a bank-to-turn autopilot, similar to an aircraft. The JDAM autopilot has four modes.
They are Rate Capture, AOA Capture, Roll Capture and Guided Flight. When guidance transitions into the
Optimal Guidance mode, the autopilot starts and enters the rate capture. During this phase, the separation
induced roll, pitch and yaw rates are reduced to acceptable levels. Once this is achieved, the autopilot
enters the AOA capture phase, which reduces any AOA remaining after rate capture to acceptable levels.
Following the AOA mode, the autopilot enters the roll capture mode, which rolls the weapon to the desired
initial flight attitude. Assuming the target is on boresight, the initial flight attitude for the GBU-31X(V)1
is a “+” configuration with the fixed fin down. For the GBU-31X(V)3, GBU-38/54, the initial flight
attitude is an “X” configuration with the fixed fin up and to the left. Once the roll attitude is established,
the autopilot enters the guided flight mode during which control fin deflections are commanded in response
to guidance commands. The transition and duration of each autopilot mode is a function of the separation
characteristics and the JDAM variant.
50
Boeing Report 15J0089
May 1, 2015
Flights with malfunctioning flight controls will result in the weapon flying in a ballistic like trajectory or
the weapon entering into a “coning” or “tumbling” motion, characterized by high roll, pitch and yaw rates
and high AOA. The resultant drag from coning or tumbling will significantly reduce down range travel.
Usually, the failed weapon will fall at or short of the ballistic trajectory of a “dumb” bomb along the
weapon flight path at the time of the failure. For minimum range releases, or for flight control failures late
in the flight, the weapon may impact downrange of the target (long). With failed flight controls, the weapon
is unable to complete the required pull down maneuver to intercept the planned impact vector. The result is
a ballistic path from the point of failure to impact, with down range travel greater than a JDAM with
functioning flight controls. Flight control malfunctions or failures can be caused by a TAS failure, failure
of the TAS to unlock the control fins, failure of a single control fin actuator, or a weapon power failure
after weapon release. The occurrence of these failures in flight test and operational use has been very low;
however, a single occurrence in a tactical environment could be catastrophic. Therefore, to reduce the
probability of collateral damage or ‘friendly fire’ from a JDAM failure, JDAM missions should be planned
with a clear path from release point to the planned impact point plus 1 nm down range of the planned
impact point when the tactical situation permits.
JDAM combines weapon maneuverability and optimal guidance to allow attack of horizontal and vertical
targets over large footprint areas, enhancing mission planning flexibility and aircraft survivability. Figure
8.18 shows an example of the footprints that can be achieved from 40,000 ft with a MK-82 JDAM against a
horizontal target, and Figure 8.19 shows the same scenario against a vertical target. Detailed footprints for
other conditions are contained in the Manual Mission Planning section. Footprints define the weapon
performance for a given set of release conditions, planned impact angle/azimuth, and environmental
conditions. The JDAM OFP contains an In Weapon LAR (IWL) algorithm that generates the
LAR/footprint. However, specific aircraft models may or may not interface and display the IWL. The
manual mission planning section shows footprints generated by the IWL.
Given a specific release profile and environment, impact angle tolerances can substantially change the size
of a footprint. JDAM LARs and footprints are often referred to interchangeably; LARs define the region in
which the aircrew can release the weapon and prosecute a specific target, while the footprint defines a
targeting area on the ground relative to the current aircraft position. The IWL subsystem provides an
In_Range and an In_Zone LAR solution. In_Range footprints define weapon performance with a 12 foot
guidance miss constraint. In_Zone footprints are defined by a 12 foot miss constraint and a +/- 8 degree
conical impact tolerance. The conical tolerance applies to the commanded impact angle and commanded
impact azimuth specified. Therefore, for a 60 degree impact angle command, the In_Zone footprint defines
a region within which the weapon will achieve an impact angle between 52 and 68 degrees. For a valid
commanded impact azimuth, total angular error based on impact angle and impact azimuth will not deviate
from the commanded impact vector more than 8 degrees.
For aircraft which do not display the GBU-54 IWL, an alternate method, such as a kneeboard card or de-
rating, will be required to supplement the GBU-38 displayed LAR.
51
Boeing Report 15J0089
May 1, 2015
52
Boeing Report 15J0089
May 1, 2015
JDAM does not have an onboard air data system for measuring static and dynamic air pressure. Air data is
calculated using an Air Data Estimator (ADE) based on environmental data provided in the aircraft
environmental message and updated with JDAM measured longitudinal acceleration (deceleration). ADE
accuracy is important for reaching targets at the footprint perimeter because it allows full use of vehicle
AOA capability while maintaining low flight controls risk. High ADE Accuracy also improves autopilot
robustness throughout the AOA/Mach envelope.
For MK 82 series warheads (MK 82 and GBU-54 variants), the coefficient of drag between slick and
thermally protected warheads is large enough to affect the ADE. Recognizing this, JDAM implements two
versions of the ADE. The first assumes a slick warhead (Slick ADE). The second assumes a thermal
protected warhead and is a compromise between thermal protected and slick warheads (Centered ADE). If
an aircraft ID is not provided, a Centered ADE is used as a suitable compromise. Footprints for the Slick
and Centered ADE are different. Selection of the type used is dependent upon whether or not an aircraft
identifies itself during the initialization phase. If the aircraft does not identify itself, the warhead type is
assumed unknown and the Centered ADE is used. While either will work for a slick weapon, a Slick ADE
is preferred and will provide the best performance and robustness. The differences between the Slick ADE
and the Centered ADE will affect weapon performance and should be considered during mission planning.
The detailed GBU-38 series footprints contained in the Manual Mission Planning section of this report
show examples of these differences for various release conditions. Also, the LAR footprint plots shown for
baseline JDAM performance in Section 8.6 below assume a Slick ADE and warhead.
Given highly accurate WGS 84 target coordinates, a preplanned mission will generally produce
the best accuracy.
Given inaccurate or no target coordinates, use onboard targeting if the coordinate generation
accuracy meets tactical requirements.
When onboard targeting systems are used to derive target coordinates, use of RT is recommended.
When onboard targeting systems are used to derive target coordinates and denial of GPS is
expected, it is still advisable to select RT.
When RT is used, the time interval between target designation and weapon release should be
minimized to limit the chance that the aircraft handoff error imparted to the computed target
coordinates is different than that imparted to the JDAM at release.
53
Boeing Report 15J0089
May 1, 2015
When the tactical situation permits steep impact angles will minimize miss distance due to elevation
(altitude) errors associated with aircraft handoff, weapon navigation, and Target Location Error (TLE).
Elevation error will cause the JDAM to guide to a point above or below the target. The impact error
associated with the elevation error is a function of the impact vector. Given an elevation error, a shallow
impact vector will generally result in a larger miss distance than a steep impact angle. Figures 8.20, 8.21
and 8.22 graphically depict the contribution of impact angle to miss distance. One possible drawback to
planning a steep impact angle mission is that the 85 degree and greater in-zone Launch Acceptable Region
(LAR) is smaller than the 60 degree and greater LAR.
54
Boeing Report 15J0089
May 1, 2015
Figure 8.22 INS-Only System Performance as a Function of Impact Angle and Vertical Error
55
Boeing Report 15J0089
May 1, 2015
JDAM is a Bomb-on-Coordinates (BOC) weapon, which requires the input of accurate target coordinates
(latitude, longitude and altitude) via mission planning, on-aircraft targeting systems or manual entry in the
cockpit. To ensure JDAM specification weapon system accuracy Target Location Errors (TLE)
requirements must be met (see Section 8.1.1.2). Target coordinates from the most accurate source usually
include TLE estimates. Consider using TLE estimates for employment decisions consistent with the tactical
situation. Target coordinate accuracy from onboard aircraft system targeting, Ground Forward Air
Controllers (GFAC) systems, Forward Air Controller Airborne systems and other third party systems are a
function of the targeting system characteristics, the skill of the operator, and the accuracy and reliability of
the target coordinate transmission, from the source, through the aircraft interface to JDAM.
Target coordinates and altitude are all referenced to a (World Geodetic System) WGS-84 coordinate frame.
Target altitude can be provided to the weapon using either a Mean Sea Level (MSL) geoid model or Height
Above Ellipsoid (HAE) model, as defined below:
Target elevation passed to the weapon as MSL is converted to HAE by JDAM for use in the guidance
control laws. Conversion from WGS-84 /10 MSL to HAE uses a table with values every 10 degrees in
Latitude/Longitude. Likewise, if target altitude reference is provided as EGM96 MSL, the weapon will first
convert the MSL target altitude to HAE using the EGM96 geoid model. Conversion from MSL to HAE is
linearly interpolated between table values, which can result in 2 to 6 meter altitude error.
Furthermore, certain JDAM host aircraft hard code the altitude reference bits provided to the JDAM to
indicate the WGS-84/10 geoid model, but mission planners may provide an MSL altitude based on the
EGM96 geoid model, assuming that the later model is inherently more accurate. This causes an additional
altitude error to be induced within the JDAM because of the mismatch between the geoid models.
When possible, provide target altitude referenced to HAE. When not possible, ensure that the method used
to compute the MSL altitude is consistent with the altitude reference bits provided to the JDAM.
A GPS Quality Handoff means the aircraft navigation system is achieving maximum performance. This
usually means that aircraft INS horizontal position, vertical position and three axis velocity data is GPS-
aided using an aircraft GPS system tracking multiple satellites with a low Figure of Merit (FOM). Aircraft
specific aircrew procedures should ensure that extended INS alignments, Zero velocity updates, and other
aircraft navigation accuracy enhancement processes are routinely performed on aircraft employing JDAM.
Aircraft handoff errors affecting weapon accuracy may be degraded by loss of aircraft GPS and aircraft
navigation system malfunctions. For some aircraft, the accuracy of the aircraft navigation system may also
degrade after certain types of maneuvers. For weapon INS-Only navigation, increased handoff error will
result in larger weapon miss distance. The severity of aircraft INS degradation, and the available cockpit
indications of degraded aircraft navigation system performance, should be fully defined in the aircraft
specific –34. This will improve aircrew situational awareness and enable proper JDAM employment
decisions consistent with the tactical situation.
56
Boeing Report 15J0089
May 1, 2015
8.3.1.4 Ensure Good Quality Weapon Transfer Alignment (TXA) State prior to Release
Good TXA Quality and NAV Quality will minimize the JDAM drift during INS-Only navigation. Aircraft
specific cockpit displays and procedures should ensure a good quality TXA is attainable prior to release.
When possible, release with TXA Quality of 1 and NAV Quality GOOD. Always release with GPS enabled.
JDAM GPS-aiding requires the aircraft to properly initialize the weapon GPS receiver prior to launch.
Weapon GPS initialization data requires the aircraft to provide valid ephemeris data, GPS crypto keys,
accurate time, and almanac data. The weapon will report a ‘Min GPS Data’ status of true after the GPS
receiver has been properly initialized. Invalid data will inhibit successful weapon GPS acquisition and
track. Aircraft specific procedures should identify cockpit displays to identify a lack of valid GPS
initialization data and the troubleshooting processes to correct GPS initialization anomalies. Delivery
profiles should provide JDAM time-of-flight of 32 seconds or greater to ensure sufficient time for GPS
satellite acquisition and GPS Loop Closure, and time for steering out navigation errors prior to impact.
When possible, release with All-Up-Round (AUR) Ready status with a planned weapon time of flight > 32
seconds. Releasing with a NAV Quality of MARG or Min GPS Data status of true is also acceptable.
JDAM uses the available energy at release to reach the target and achieve the planned impact vector (see
Table 8.4). Adverse separation environments (e.g. high dynamic pressure (qbar), high airspeed releases)
and adverse winds expend energy and limit the energy available for flying the required guidance trajectory.
A high fidelity 6 degrees of freedom (6DOF) model is available to the aircraft user community. The 6DOF
predicts weapon performance under any combination of atmospheric conditions (including adverse winds).
The delivered 6DOF does not model the proximity aerodynamics involved with weapon separation. This is
due to the large number of aircraft using the JDAM weapon. The modeling of every flow field associated
with each aircraft and each aircraft load out is beyond the present 6DOF capability. If winds are not taken
into account by mission planning or cockpit LARs, the weapon might not meet the intended impact
conditions, or as a worst case, will miss the target. Aircraft LARs need to compensate for adverse
separation environments and release winds.
Usually, for high altitude level JDAM releases, the separation affects can be ignored. Plan to release JDAM
near the center of the In-Zone LAR when adverse separation or wind environments are suspected and have
not been taken into account by mission planning or cockpit LARs.
Missions planned with offset impact azimuths may result in the weapon making an initial turn away from
the target, which may further increase the effect of adverse wind environments. If winds are not taken into
account in the mission planning or cockpit LARs, it is best to plan JDAM missions to fly direct from the
release point to the target. Whenever possible, consider any adverse flight environments on aircraft LAR
predictions and weapon performance prior to weapon release.
Given highly accurate WGS 84 target coordinates, a preplanned mission will generally produce the best
accuracy. When preplanned target coordinates are derived from mensurated sources, the TLE associated
with those coordinates is generally better than the TLE associated with onboard targeting systems. Aircrew
should be aware of the TLE expected for their targeting system and should be provided information from
57
Boeing Report 15J0089
May 1, 2015
the source as to the TLE for the preplanned target coordinates. Note that the TLE associated with target
coordinates from each source is the determinate for which source to use, not the target coordinates
themselves. Target coordinates from the mensurated source and the onboard targeting system could
possibly be nearly the same, but this does not mean that the weapon will impact at the same location. With
onboard targeting system coordinates and RT selected, JDAM will guide to an impact point referenced to
the aircraft navigation position at release. For preplanned target coordinates, JDAM will guide to an impact
point referenced to true WGS-84.
Given inaccurate or no target coordinates, use onboard targeting if the coordinate generation accuracy
meets tactical requirements. When the onboard targeting system TLE is known and is acceptable for the
tactical situation, target coordinates from the onboard targeting system are better than what can be expected
from inaccurate or unknown coordinates.
When onboard targeting systems are used to derive target coordinates, use of RT is recommended. Use of
RT will effectively eliminate the aircraft position handoff error and the aircraft handoff velocity errors. It
will also limit JDAM IMU drift to a one second interval since GPS updates every second vice incurring the
IMU drift for the total TOF.
When onboard targeting systems are used to derive target coordinates and denial of GPS is expected, it is
still advisable to select RT. If RT is not used, and JDAM does acquire GPS, the navigation reference will
be reset to a GPS coordinate reference vice a relative reference. In this case, aircraft position handoff error
becomes a component in the system miss and a larger miss can be expected.
When RT is used, the time interval between target designation and weapon release should be minimized.
RT expects a common position handoff error for generation of the target coordinates and navigation after
release. If navigation handoff error is changing and there is a significant time interval between coordinate
generation and release, the handoff error reference will be different. The result will be additional system
miss.
The key factors for optimizing baseline JDAM accuracy are summarized in Table 8.6.
GPS-INS Guidance
58
Boeing Report 15J0089
May 1, 2015
Ensure GPS Quality Aircraft Handoff Ensure aircraft GPS and navigation systems are
fully functional and aircraft navigation is GPS-
aided with a low GPS FOM.
Be aware of aircraft maneuvers or aircraft
navigation system modes that degrade aircraft
navigation system accuracy and factor degraded
aircraft system performance into LJDAM
employment decision.
Enable GPS-aided Navigation Valid Ephemeris, Keys and Time
Time of flight > 24 seconds
Non-denied GPS environment
Ensure High Quality LJDAM Transfer Alignment State 01/Good
Minimize TLE Use most accurate target location source (TLE
requirements are relaxed for laser guidance).
Plan Steep Impact Angle If possible, plan steep impact angles to
eliminate target altitude error concerns (steep
impact angle requirements are relaxed for laser
guidance).
Compensate for Flight Environment Consider winds and any atmospheric or
separation environments that affect weapon
performance when mission planning, and
aircraft LAR development.
Laser guidance improves accuracy for fixed horizontal and vertical targets from 5 and 6 meters to 3 and 4.5
meters respectively and adds a moving target capability. This improvement results from the ability of laser
tracking to account for larger TLEs. Basic assumptions and factors applicable to laser guidance are
summarized as follows:
Fixed Targets
TLE at weapon release less than or equal to 37m.
Conditions to support sufficient acquisition range (3km for fixed targets).
Uninterrupted laser designation of the target aim-point for the last 3km of free flight prior to
impact (approximately 8 to 15 seconds depending on terminal velocity) prior to impact.
59
Boeing Report 15J0089
May 1, 2015
Moving Targets
Horizontal constant velocity target.
TLE at weapon release less than or equal to 37m with less than 5 seconds targeting latency.
Conditions to support sufficient acquisition range (4km Sfor moving targets).
Uninterrupted laser designation of the target aim-point for the last 4km of free flight prior to
impact (approximately 15-20 seconds prior to impact).
Tail chase for fast movers is defined as follows:
o Target heading provided to the weapon at release is within +/-22° of the actual target
heading at release.
o Aircraft heading at release is within +/-45° of the actual target heading.
8.3.2.2 Long Last Pulse Logic versus Short Last Pulse Logic
When lasing a target from an airborne pod or a ground designator, any obscurant (e.g. smoke, fog, haze)
between the target and designator may result in reflected laser energy from the obscurant instead of the
target. This can degrade weapon accuracy since the weapon does not track the desired target. When ground
lasing, this can be a safety issue since the obscurants may cause the weapon to steer towards the ground
designator and put the Forward Air Controller in danger. Also, with ground fog or smoke, the track point
can move back along the designator beam and impact close to the ground designator. Long Last Pulse
Logic (LLPL) is less susceptible to obscurants in these scenarios. Short Last Pulse Logic (SLPL) is used
when a ground designator illuminates a target at long range and a portion of the designator energy spills
over the target, illuminating trees or other objects close behind the target. If the laser sensor tracks the last
pulse in this scenario, the weapon will track towards the object(s) behind the target. SLPL reduces the
probability of tracking illuminated items behind the desired target by rejecting small signal returns from
longer ranges. See section 8.4.1 for setting the last pulse logic via panel settings on the sensor assembly.
The key factors for optimizing LJDAM accuracy, when laser guidance is not expected, are summarized in
Table 8.6. Additional optimizing factors for laser guidance are summarized in Table 8.7.
60
Boeing Report 15J0089
May 1, 2015
Laser Guidance
Maintain Laser Spot on Target Ensure spot is maintained on target (no leading
or biasing of the aim-point).
Weapon performance is relative to laser spot.
Continuous Lasing in Terminal Phase Ensure continuous lasing 4km range-to-go
before impact (~15 sec before impact)
No penalty/degradation for early lasing
Performance degrades with laser cut-off in
terminal phase.
Laser Designation relative to LJDAM Impact Angle Laser designation Line of Sight (LOS) angle to
target is within +/- 45° of weapon approach
LOS (consistent with LGB conops). Maximizes
probability of early laser acquisition.
Laser Designation Range Within 5nm slant range during terminal phase
(airborne designation)
Within 1nm range during terminal phase
(ground designation)
Maximizes probability of early laser
acquisition. Performance will degrade if
acquisition is <4km for moving targets and
<3km for fixed targets.
Laser Code Available Range: 1111 to 1788
The update rate or laser pulse rate is fastest for
the lower number codes (1111 20 Hertz) and
slowest for the higher number codes (1788 < 10
Hertz).
LJDAM Relative Targeting Mode For onboard targeting systems, use relative
targeting mode if available.
Additional discussions of the key points for laser guidance are as follows:
Performance is maximized by ensuring a Laser designation Line of Sight (LOS) angle to target is within +/-
45° of weapon approach LOS. This is consistent with LGB lasing requirements defined by JP 3-09.1, Joint
Tactics, Techniques and Procedures for Laser Designation Operations. The laser energy seen by LJDAM is
reduced as the Laser designation Line of Sight (LOS) angle to target increases. Some of the laser energy
may impinge on parts of the target not visible to the LJDAM field of view. JP 3-09.1, Joint Tactics,
Techniques and Procedures for Laser Designation Operations calls this the podium effect and this effect
applies to all lasing when the target surface lased is vertical.
Table 8.8 summarizes the specification assumptions for designation range for LJDAM (actual targeting pod
performance will vary). Accuracy performance will degrade if acquisition is <4km for moving targets and
<3km for fixed targets. Energy losses occur primarily at lower altitudes (<20kft MSL). Designation at
higher altitudes will not significantly change the laser designator beam attenuation; however, it may cause
the laser spot to grow in size where it will be larger than the typical target. Laser energy not falling on the
target may cause a reduction in acquisition range. Also the effects of designation beam jitter become more
pronounced and may cause a reduction in accuracy.
61
Boeing Report 15J0089
May 1, 2015
For moving targets, LJDAM derives velocity information from the movement of the target/spot to compute
a predicted impact point. Laser beam divergence and laser designator stability can affect overall system
level accuracy performance. In general, these effects are minimized at shorter designation ranges.
40 mph moving target heading in line with aircraft heading, impact angle command of 70 deg, no
velocity bias information provided to the weapon
70 mph moving target heading in line with aircraft heading, impact angle command of 69 deg, 60
mph velocity bias provided to the weapon
Horizontal stationary target, impact angle command of 70 deg
Figure 8.23 shows a representative effect on CEP performance as a function of the LOL range-to-target in
the case where laser measurements are never reacquired during flight. Figure 8.24 through Figure 8.26
represent an intermittent LOL, where the laser sensor initially acquires measurements, experiences LOL,
and then reacquires laser measurements for the remaining portion of flight. Each curve in these figures
corresponds to an initial range-to-target where the weapon experiences LOL and each dot on the curve
corresponds to the duration of the LOL.
Specific scenario variations, such as acquisition range and Laser code PRF, may result in some variation in
the specific performance. However; these results demonstrate the importance of providing nearly continual
laser designation throughout the last 4.5 km of the LJDAM terminal engagement. In particular, the laser
measurements received in the 1 to 1.5 km range-to-go are critical to achieving high accuracy. This is
because these measurements tend to be the least noisy and provide guidance with some of the best
measurements for determining the final target intercept location.
62
Boeing Report 15J0089
May 1, 2015
40
40 MPH
MPH0 0Hdg
Hdg68 Deg
70 Deg 70
70 MPH
MPH6060
MPH BiasBias
MPH 0 Hdg
0 69
HdgDeg
70 Deg 70
70 Deg
DegStatic
StaticTarget
Target
30
• Release @ 20K ft HAT, 0.85M, Level Flight, No
Winds
25 • 4 Km Acquisition Range, 20 Hz Pulse Repetition
Frequency (PRF) 70 mph, 60 mph Target
Vel Bias Handover
Miss CEP (m)
20
40 mph, No Target Vel
Handover
15
Target Stationary, No
Velocity Handover
10
0
0 0.5 1 1.5 2 2.5
Range at LOL (Km)
duration
1.5 Km
15 Initial LOL
2 Km
Initial LOL
10 1 Km Initial LOL
0
0 1 2 3 4 5 6 7
Loss of Laser Designation Duration (sec)
Figure 8.24 - Intermittent Laser Designation Interruption CEP Sensitivity, 40 MPH Moving Target
with no Velocity Bias Handover
63
Boeing Report 15J0089
May 1, 2015
1.5 Km
Initial LOL
15
2 Km
Initial LOL
1 Km Initial LOL
10
0
0 1 2 3 4 5 6 7
Figure 8.25 - Intermittent Laser Designation Interruption CEP Sensitivity, 70 MPH Moving Target
with 60 MPH Velocity Bias Handover
70 Degrees, Static
30
20
Miss CEP (m)
21.3 m CEP
@ 6.07 sec
15
(2 km)
1.5 Km LOL
Initial LOL 2 Km duration
Initial LOL
10
1 Km Initial LOL
0
0 1 2 3 4 5 6 7
64
Boeing Report 15J0089
May 1, 2015
LJDAM accuracy is a function of the laser spot being tracked during the terminal phase. In the event that
multiple designators are lasing the target with the same PRF laser code and these multiple designations are
within the field-of-view of the LJDAM sensor, the following should be considered.
The initial designator that the LJDAM acquires and tracks is somewhat arbitrary, presuming more
than one designation is visible in the field of view of the sensor. At initial acquisition, it requires 3
to 4 pulses to acquire and track.
Once it has locked onto a particular designator, it is highly unlikely it will track other designators
in the field-of-view, unless loss-of-lock occurs (for instance, if the pod quits lasing). It takes a
loss of 4 pulses to declare loss-of-lock.
Once loss-of-lock occurs, the LJDAM will attempt to reacquire a laser spot in the field-of view.
As noted above, if there are still multiple designators in the field of view, it is somewhat arbitrary
which signal the LJDAM will acquire and track.
In summary, for the multi-designator scenario described (same PRF laser codes within sensor field of
view), it is highly likely that the LJDAM sensor will only track one designator and will not jump to an
alternate designator unless loss of lock occurs on the original tracked designator.
In the scenario of switching designators (i.e. goalie approach switching designation from aircraft 1 to
aircraft 2) during the last 15-20 seconds of weapon guided flight, the weapon will go through the above
process for loss-of-lock and re-acquisition of the laser designator. For a laser code of 1688 (10 Hz PRF),
the laser sensor will lose a minimum of 0.7 seconds of usable laser measurements.
For aircraft that cannot distinguish a GBU-54 from a GBU-38, the pilot can inadvertently select the wrong
weapon for a specific mission. For this reason, mixed loading of the two variants is not advised.
Flight through rain or hail may subject the seeker window to various degrees of pitting which can affect the
normal function of the weapon causing degradation in the weapons accuracy proportional to the amount of
pitting on the sensor window. To decrease the possibility of window pitting effects, when encountering
visible moisture enroute to the target, navigate around the moisture or transit the area at the minimum
practical true airspeed.
65
Boeing Report 15J0089
May 1, 2015
Laser Code and Pulse Logic Selection: The laser code and pulse logic selection (short last pulse or long
last pulse) are set via panel settings on the bottom of the Sensor Assembly (see Figure 8.27). The laser code
can be set from 1111 through 1788. Set the first code switch setting to a 1L (long last pulse) or a 1S (short
last pulse) to match mission requirements. Selecting either of the "blank" switch positions on either side of
the 1L position is the same as selecting 1S. THE DEFAULT FIRST CODE SWITCH NUMBER SETTING
SHOULD BE 1L IF NOT OTHERWISE SPECIFIED.
If the first code switch is set to position 5 thru 8 (tick mark position), and/or the second code switch is set to
an ‘8’ and an IBIT is commanded the weapon will report a JDAM CPU failure (see Figure 8.27). If either
one of the above scenarios occur, the laser code is considered invalid and will render the Laser Kit
inoperable). The panel settings are read by LJDAM at weapon power on. Any changes made to the panel
settings after weapon power is applied will not be recognized by LJDAM until the weapon power is cycled.
Invalid Settings
66
Boeing Report 15J0089
May 1, 2015
LJDAM leverages off of the existing JDAM BOC and Self-Targeting targeting modes. These modes are the
basis for providing the initial target coordinates for the LJDAM. For moving targets, a target speed bias
and heading can also be transferred by two methods. The first method uses the standard JDAM interface
and is referred to as the QRC mode. Target speeds and headings are provided to the weapon using specific
impact angle and impact azimuth commands (see Table 8.10 for LJDAM velocity bias logic). The second
method uses the full laser interface. Aircraft that integrate the full laser interface can provide target speed
and heading to the weapon directly using their respective on-board sensors (see section 8.4.6-Full Laser
Interface). The target coordinates methods of entry include preplanned, cockpit entry, and self-targeting.
Regardless of the mode or method of entry, LJDAM guidance adds the ability to update the target
coordinates for a lased target enabling the use of less accurate initial targeting data than for baseline JDAM
GPS/INS guidance. It is important to note that although LJDAM can tolerate larger Target Location Error
(TLE), the LJDAM accuracy degrades as TLE increases (see Figure 8.30 for an example of CEP
performance versus TLE for fixed targets).
If the TLE exceeds 800m there is a potential for the LJDAM to fail to acquire the lased target returns
leading to a large target miss. For this reason targeting and transfer alignment should be accomplished to
accommodate the LJDAM targeting requirements.
Because of the LJDAM’s ability to utilize reduced accuracy targeting coupled with the capability for time
critical and moving targets, it is expected that self targeting will be the most common mode. Self-targeting
can be accomplished using absolute or relative targeting data. If using absolute targeting data, the targeting
aircraft needs to have a GPS quality navigation solution and the ability to provide the target coordinates to
support a total TLE of 37 m (1 sigma). This can be accomplished by ensuring that the aircraft navigation
system is in the most accurate state and TXA status is 01/Good prior to release of LJDAM. When available,
self targeting utilizing the LJDAM Relative Targeting feature provides for successful operation with a
reduced quality aircraft navigation solution. Use of relative targeting provided just prior to launch mitigates
the effect of a large handoff error induced by inaccurate aircraft navigation while targeting, as shown in
Figure 8.6a through 8.6d. Without using the relative targeting mode, if LJDAM acquires GPS and closes
the GPS-aiding loop prior to laser sensor measurement processing (up to 4.5 km to go), the navigation
reference frame will be reset to a GPS reference creating an increase in the TLE comparable to the original
aircraft navigation error used for targeting. Additional detail on Relative Targeting is provided in section
8.2.1.1.1.
67
Boeing Report 15J0089
May 1, 2015
LJDAM employment against fixed targets is basically the same as for baseline JDAM with the added
dimension of laser updates in the terminal phase. After transitioning to the terminal laser guidance mode,
LJDAM will continuously guide to the estimated target position that has been updated by tracking the laser
energy. If laser energy is never acquired, LJDAM will guide to the target coordinates provided by the
aircraft with JDAM Specification GPS-aided accuracy. Refer to Table 8.10 for details regarding LJDAM
commands specific to the engagement of vertical and horizontal fixed targets. When an impact angle
between 45° and 90° (excluding 66° and 89°) is commanded in combination with an invalid azimuth angle,
the weapon makes no assumptions whether the target is fixed or moving. This mode allows the user to
employ the weapon against a target that is stationary, but in the event the target relocates or transitions to a
moving target, the laser spot can be used to retarget the weapon to the desired aimpoint. This provides the
operator flexibility for dynamic engagement scenarios and ultimate end game control of the weapon impact
location.
When engaging stationary targets, do not inadvertently trigger the Manual Mode velocity bias modes for
slow or fast moving targets. Although the slow mover target type will also work for horizontal stationary
targets, it is strongly suggested that the horizontal stationary target type be used since better weapon
performance occurs when the target is known to be stationary. For vertical stationary targets, use the
vertical stationary target type.
Standard LJDAM targeting data (target coordinates, impact angle and impact azimuth) are provided to the
weapon prior to release. Selection of impact azimuth in a lasing mode can provide flexibility by controlling
the weapon approach heading to the target without requiring the aircraft to modify its approach heading.
After aircraft separation, the weapon steers to the aircraft-provided target position utilizing baseline JDAM
guidance. The designating aircraft or person on the ground maintains the laser spot on the desired impact
point. LJDAM will start processing the laser energy at 4.5 km range to the target, with no performance
penalty for lasing early. Once the laser spot has been acquired, the weapon’s guidance law transitions from
the baseline JDAM optimal guidance to proportional navigation guidance. Basic rules for ensuring laser
guidance accuracy are shown below.
TLE at weapon release less than or equal to 37m
Conditions to support sufficient acquisition range (3km for fixed targets)
Uninterrupted laser designation of the target aim-point for the last 3km of free flight (typically 10
to 15 seconds depending on terminal velocity) prior to impact.
Figure 8.28 depicts the sensor Field of View (FOV) for different acquisition ranges assuming the sensor is
perfectly centered on the target location at a 70º boresight angle. Note that considerable uncertainty in
Target Location Error (TLE), compared to baseline JDAM, is allowable because the FOV covers a fairly
large area, however, the ability to engage a target is also dependent upon weapon maneuverability.
68
Boeing Report 15J0089
May 1, 2015
One major software difference between LJDAM and baseline JDAM is the modification of the guidance
law. The modified guidance law alters the baseline trajectory to optimize sensor FOV detection of the
target (see Figure 8.31 for a comparison of LJDAM vs. baseline JDAM guidance). In general, the objective
of this approach is to minimize differences with the basic JDAM footprint for GPS/INS guidance mode, as
well as ensure the target is within the sensor field-of-view during the terminal phase for lasing mode. The
combination of sensor field-of-view (ability to detect and acquire) and weapon maneuverability allows
approximately 800m correction capability at 4km acquisition range and 500m correction capability at 3km
acquisition range. For horizontal fixed lased targets, accuracy may be degraded if TLE is greater than 37m,
(1 sigma). This is because LJDAM assumes for horizontal targets that the target may be moving. Greater-
than-expected TLE at initial laser spot acquisition is initially considered target motion for horizontal
targets. The velocity assumption is eventually driven to zero when the TLE is within 37m for fixed targets.
For large TLE, some residual velocity assumptions result in degraded fixed target accuracy performance as
it takes longer to drive the estimates to zero. While CEP may increase with increased TLE, the LJDAM is
quite tolerant to large amounts of TLE. As shown in Figure 8.29, CEP is still less than 4.5m for TLE of
600m (versus a 3m CEP for 37m of TLE).
Figure 8.29 shows an example of Circular Error Probable (CEP) degradation for different values of fixed
TLE for a 20 Kft HAT, 0.85M release condition. The TLE values shown on the plot correspond to fixed
TLE offsets in eight different directions, where the 0 degree offset corresponds to a fixed positive
downrange TLE. In addition to the fixed TLE offset, the data provided was generated with a random 37 m
(1 sigma) TLE superimposed on the fixed TLE offset. This simulates, for example, pod designation of one
target location (which is the target data provided to LJDAM) and a laser designation of a different target
location, where the difference between the two locations is equal to the fixed TLE offset.
69
Boeing Report 15J0089
May 1, 2015
Figure 8.29 - Fixed Target CEP vs. Target Location Error (TLE)
Block 8 (and later) software updates have resulted in improved predicted weapon performance in taking out
large amounts of TLE. Figure 8.30 provides additional information on how CEP degrades with large
amounts of TLE for LJDAM.
70
Boeing Report 15J0089
May 1, 2015
Figure 8.30 - Fixed Target CEP vs. Target Location Error (TLE)
Figure 8.30 shows the degradation of the maximum CEP of all directions as a TLE is increased. In this
scenario, CEP values are expected to remain under 5 meters for TLEs out to 600 meters. Note that these
results are specific to the conditions analyzed. In this case the target is in the center of the footprint. It is
expected that the maximum CEP would increase as the target approaches the edge of the footprint (i.e. the
limits of the weapon’s kinematic range).
Although the laser sensor may detect the laser spot anytime after release from the aircraft, the weapon
guidance itself does not use laser updates until it is within 4.5 km of the target location. The weapon will
transition to proportional guidance after the combination of first target acquisition and the weapon is within
4.0 km range-to-go, or if the weapon is within 3 km range-to-go without target acquisition, whichever
occurs first. At that point, GPS updates from the onboard GPS system are inhibited if valid laser
measurements are processed. After transitioning to terminal guidance, the weapon remains in that mode
regardless of the status of laser lock; no alternating between guidance laws is performed. Once GPS
updates are inhibited due to processing of valid target acquisition measurements, the GPS updates are
inhibited for the remainder of the flight regardless of the status of laser lock. If valid target acquisition
measurements are not received during the terminal guidance phase, GPS updates will not be inhibited. If
LJDAM is commanded to inhibit laser guidance and fly baseline JDAM guidance, then no laser
measurements are processed.
For commanded impact angles of <45º, the target is assumed to be a fixed vertical target. For commanded
impact angles of 66º or 89º, LJDAM assumes a fixed horizontal target. In these cases, Angle of Attack
(AOA) is collapsed at 0.6 sec time to go and the incidence angle at impact will typically be less than 2º.
For commanded impact angles of >45º (except 66º or 89º), the target is not assumed to be fixed. In this
case, AOA is not collapsed in order to maximize weapon maneuvering and accuracy against moving
targets. When angle-of-attack is not collapsed, typical AOA at impact will be approximately 12º
(determined analytically, with a 6º standard deviation).
71
Boeing Report 15J0089
May 1, 2015
20000
Laser
8 nmi Downrange Target
15000 JDAM
Altitude (ft)
20000
10000
Baseline
Baseline JDAM
10000
5000 JDAM
Laser
0
JDAM
0
0 5000 10000 15000 20000 25000 0 10000 20000 30000 40000 50000
Downtrack (ft) Downtrack (ft)
Employment of LJDAM against moving targets requires a targeting pod or ground-based designator that
can track the target (either manually or automatically) and must account for target motion and predicted
target position at laser acquisition. LJDAM has the capability to receive both target position and velocity
from the aircraft when the full laser interface is implemented in the aircraft. When the aircraft interface
cannot provide the necessary information, a workaround solution (sometimes referred to as QRC mode or
manual mode) has been mechanized. Using the standard aircraft to JDAM interface, LJDAM provides the
capability to engage targets moving from zero to 70+ mph. Slower moving targets can be engaged with no
special consideration for target heading or impact angle but for faster moving targets, it is necessary to
provide target velocity bias information to the weapon to ensure the target can be detected and engaged. To
achieve this, the aircrew may specify an approximate target speed and heading (velocity bias) utilizing
Impact Angle and Impact Azimuth. The weapon will then utilize this data to compute and guide to a
predicted intercept point after release. The logic for the overall LJDAM manual mode implementation is
summarized in Table 8.9.
72
Boeing Report 15J0089
May 1, 2015
The basic concept for using target velocity bias is provided in Figure 8.32. To engage moving targets, the
operator must keep the laser spot on or around the vehicle. Do not lead the target with the laser spot
because the weapon is using the laser spot information to predict the actual targets speed, direction and
estimated intercept position.
73
Boeing Report 15J0089
May 1, 2015
Standard LJDAM targeting data (target coordinates, impact angle, and impact azimuth) is provided to the
weapon prior to release. If a target velocity bias is not provided, the weapon will fly optimal guidance to a
phantom aimpoint relative to the target coordinate provided by the aircraft. When laser energy is tracked
inside 4.5 km from the target, the target velocity and position is updated continuously at the laser code
pulse repetition frequency (PRF). The weapon will then adjust its trajectory as necessary to steer to the
updated target intercept coordinate. If a laser spot is never acquired, the weapon functions in a bomb-on-
coordinates (BOC) mode and guides to the target coordinates provided by the aircraft with JDAM GPS-
aided accuracy.
If a target velocity bias is provided, the weapon estimates the expected target intercept position post launch
using the target coordinates provided by the aircraft and the corresponding target velocity bias. When laser
energy is tracked inside 4.5 km from the target, the target position and velocity is updated continuously at
the laser code pulse repetition frequency (PRF). The weapon will then adjust its trajectory as necessary to
steer to the updated target intercept coordinate. If a laser spot is never acquired, the weapon steers to the
target location projected in time, based on the target coordinates and velocity bias provided at weapon
release. If a laser spot has been acquired and becomes either intermittent or lost, the weapon continues to
steer to the current best estimate of target intercept location, including a correction for target velocity. If the
laser spot is reacquired, LJDAM resumes updating of the target intercept location.
For fast moving targets, a tail-chasing tactic is recommended to ensure expected accuracies are achieved. In
addition, LJDAM generally provides more robustness to wind conditions for more direct tail-chasing.
Figure 8.33, depicts the effect of the target velocity bias. The target Area of Uncertainty (AOU) is shown
for 20 mph, 40 mph, 60 mph and 80 mph moving targets heading in any direction for a typical LJDAM
Time of Flight (TOF) required to reach a 4.5 km slant range (Note: The release scenario corresponds to a
condition where a 40 second total TOF to impact for stationary targets is expected). Representative ideal
LJDAM seeker FOVs at a 4.5 km slant range to the target are shown for the cases where no bias is
provided, a 40 mph bias is provided and a 60 mph bias is provided. The “predict ahead aim-point” and the
sensor FOV are displaced in the direction of the target heading when a velocity bias is provided. This
depiction shows the importance of providing an impact azimuth so that LJDAM can move the predicted
impact location in the proper direction. Note that the seeker FOV may cover a target with a velocity that
deviates significantly from the bias provided even when the planned impact azimuth fairly closely matches
the target direction; however, the planned impact azimuth must match target direction more closely as
target speed increases. As the target AOU becomes larger, the seeker FOV at the displaced aim-point
covers less of the AOU.
74
Boeing Report 15J0089
May 1, 2015
This discussion assumes that LJDAM accuracy factors are accounted for. Accuracy factors such as
excessive handoff error, poor transfer alignment, excessive targeting pod LOS or ranging errors, or inability
to use the LJDAM relative targeting mode can cause the lased target to be outside of the seeker FOV at
predicted laser acquisition ranges. In addition, it is necessary to understand the time latency between target
coordinate determination and when the target information is sent to LJDAM, especially in the case of off-
board targeting. Figure 8.33 assumes zero aircraft targeting latency. Latency will increase the target AOU
as a function of the target speed and latency time. As an example, a latency time of 5 seconds for a target
moving at 60 mph adds about 430 ft (130 meters) to the radius of the AOU. (Note: AOU radius = target
speed * (TOF to reach 4.5 km slant range + aircraft latency))
The Block 8 and later LJDAM OFP includes an update to the PTT algorithm (LJDAM’s target state
estimator) that includes an acceleration detection logic loop. This design improves maneuvering target
performance while maintaining stationary target and uniform velocity performance. Table 8.10 shows the
predicted Maneuvering Target Capability.
Performance Prediction Summary
Target Speed (MPH) Maneuvering Capability
0 - 40 ~4m CEP for up to 0.5g targets
40 - 70 ~5m CEP for up to 0.2g targets
70 - 90 ~7m CEP for up to 0.2g targets
Simulation data indicates that the GBU-54 is effective against non-maneuvering targets exceeding 70
MPH, is effective against non-evasive maneuvering targets (≤ 0.2 g’s) up to 70 MPH and is effective
against evasive maneuvering targets (≤0.5 g’s) up to 40 MPH.
75
Boeing Report 15J0089
May 1, 2015
LJDAM has been fielded under a Quick Reaction Capability (QRC) program designed to rapidly meet an
Urgent Operational Need to engage moving targets. The employment restrictions and guidelines are set in
place for aircraft using the QRC mode (a.k.a. Manual Mode) of operation which utilize the GBU-38 JDAM
aircraft to weapon interface and Rule of Thumb (ROT) data for weapon employment.
LJDAM is capable of level, dive and loft releases over the entire JDAM release envelope. Based on the
current USG requirements, data in this document only covers level weapon releases for lasing mode from
altitudes of 10K to 35K Height-Above-Target (HAT). For GPS-aided mode, releases may be executed
within the baseline JDAM limits documented in Table 8.10.
There is no operational restriction on target speed or target maneuvering for engagement. The following
flight tests have been conducted prior to the release of this document to verify weapon performance for the
following engagement scenarios:
• Constant Velocity Targets up to 85 mph, release altitudes of 15,000 HAT and above.
• Constant Velocity Targets up to 50 mph, release altitudes below 15,000 HAT.
• Maneuvering Target up to 55 mph, performing various non-evasive and evasive maneuvers up to
0.5g's
• Stationary Targets with up to 100 meter of target location error
• GPS-aided only (non lasing) stationary targets
LJDAM is capable of captive carriage, jettison and employment (specific aircraft may have limitations
below what the LJDAM is capable of withstanding) as presented in Table 8.11.
76
Boeing Report 15J0089
May 1, 2015
LAR/Footprint
Target Cross-range Ax is
Footprint Boundary
LAR Boundary
LAR Footprint
Dow n-range Ax is Dow n-range Ax is
Rules of Thumb, or ROTs, are downrange release distances to a target for a given set of release,
environmental and target conditions that result in the weapon meeting the accuracy requirements. They
have been developed for the LJDAM program to provide a means of employment for aircraft that utilize the
standard JDAM interface. The ROT release point to the target is computed using a large number of LARs
(50 to 100) to determine the valid release point for a wide variety of release, environmental and target
conditions. A simplified example of how a ROT is determined can be seen in Figure 8.35– LARs vs. ROT
comparison.
77
Boeing Report 15J0089
May 1, 2015
LAR/Footprint
Target Cross-range Ax is
Rule of Thumb
(ROT)
LAR
Intersection
ROT
Box
LAR Boundary 1
LAR Boundary 2
LAR
LAR Boundary 3
Dow n-range Ax is LAR Boundary 4
Figure 8.35 shows notionally how the ROT is determined from a larger set of LAR boundaries for multiple
target speeds, target directions, wind speed and wind directions. The ROT is computed explicitly and
provided in ROT tables that are shown in the Appendices.
The ROT box is defined by a nominal downrange release distance to the target plus or minus a downrange
tolerance. For a ROT to be valid, it must have minimum ROT box size of 0.6 nmi downrange and 0.6 nmi
cross range (i.e. the ROT +/- 0.3 nmi). Note that the ROT boxes shown are for the specific conditions in
each table and represent the un-conservative, maximized window for which the weapon can be employed.
Similar to JDAM baseline LARs, for the greatest probability of success, it is advised to release as close to
the ROT center as possible.
Inherently, the goal of a ROT is to maximize the range of environmental and targeting conditions for which
it can be used. Thus while LAR improvements mean an increase in their size or coverage area, ROT
improvements mean an increase in the number of conditions for which a single release point is valid (i.e.
more wind directions, target directions, ranges of target speeds, release conditions, etc) or, for the same
conditions, an increase in the length or width of the ROT box. ROTs are intended to provide a simple
means of employing LJDAM by aircrew operating without the benefit of a LJDAM moving target LAR.
Air data estimator for Laser JDAM is implemented the same way as the MK-82 JDAM. It is estimated
based on environmental data provided by the aircraft environmental message and updated with LJDAM
measured longitudinal acceleration (deceleration). ADE Accuracy is important for reaching targets at the
footprint perimeter because it allows full use of vehicle AOA capability while maintaining low flight
controls risk. High ADE Accuracy also improves autopilot robustness throughout the AOA/Mach envelope.
For MK-82 series warheads, the difference in the drag coefficient between slick and thermal protected
warheads is large enough to affect the ADE. Recognizing this, LJDAM implements two versions of the
78
Boeing Report 15J0089
May 1, 2015
ADE. The first assumes a slick warhead (Slick ADE). The second thermal protected is a compromise
between thermal protected and slick warheads (Centered ADE). If an aircraft ID is not provided, a
Centered ADE is also used as a suitable compromise. Footprints for the Slick and Centered ADE are
different. Selection of the type used is dependent upon whether or not an aircraft identifies itself during the
initialization phase. If an aircraft identifies itself, a slick warhead is assumed and the Slick ADE is used. If
the aircraft does not identify itself, the warhead type is assumed unknown and the Centered ADE is used.
Kneeboard card development can use either version since both a Slick and Centered ADE are implemented
in the LJDAM 6DOF and Range Tool.
Matching the ADE configuration to the weapon configuration has proven essential for optimum range
performance. Cockpit LARs and ROTs will be overly optimistic for this mismatched ADE/warhead
configuration. LAR derating factors for this mismatched ADE/warhead configuration have been developed
for the GBU-38 configuration, but not the GBU-54 configuration.8.4.8 Full Laser Interface
By implementing the full laser interface, the aircraft has the capability to utilize additional LJDAM features
that are not available in the standard JDAM interface. The operator can command Laser Code settings to
override manual settings on the weapon, and the current laser code can be monitored by the aircraft.
LJDAM has the capability to process target velocity information. When tracking a moving target, the
aircraft can repeatedly refine the target position and velocity data provided to the weapon. Additional
guidance modes are available via command from the aircraft, including Inhibit Laser Guidance and Target
Known Stationary. Finally, LJDAM supports In-Weapon LAR (IWL) for all LJDAM guidance modes,
which accounts for the target velocity information provided by the aircraft if applicable.
There are two Full Laser Interface protocols that LJDAM can utilize to interface with the aircraft. They are
the JDAM Core Interface and the JDAM Universal Armament Interface (UAI). The protocol that is used
varies by aircraft platform. The details of the JDAM Core Interface can be found in Revision 8 of document
number JICD-MDA-001; titled “Interface Control Document – Joint Direct Attack Munition (JDAM) to
Host Aircraft – Core Interface”; dated 9 April 2008. The details of the JDAM UAI Interface can be found
in document number UAI-PSICD-R02; titled “Universal Armament Interface – Platform/Store Interface
Control Document”; dated 15 October 2007.
The LJDAM In-Weapon LAR (IWL) software provides weapon range and performance information to the
aircrew in the form of 9-sided polygonal LAR boundaries, entry/exit ranges and weapon Time of Flight
(TOF) information. After receiving a minimum target data set, minimum transfer alignment, environmental
data and a valid LAR format request from the host aircraft, the weapon computes the LAR data
dynamically based on the host aircraft's flight conditions, targeting parameters and atmospheric conditions.
In addition to the parameters listed above, the guidance mode that is commanded affects the IWL data and
the performance of the weapon. For this reason there are four types of IWL data that can be returned to the
aircraft. They are Baseline (no laser sensor hardware present), Laser Baseline (LBSLN), Laser Moving
Target (LMT), and Laser Target Known Stationary (LTKS).
For Baseline, LBSLN and LTKS Stationary guidance modes, separate In-Range (IR) and In-Zone (IZ) IWL
data is returned to the aircraft. The IR LAR is defined as the region or area that the host aircraft must be
within when releasing the weapon to impact the target with the defined weapon accuracy. The IZ LAR is
defined as the region or area that the host aircraft must be within when releasing the weapon to impact the
target within the defined weapon accuracy and to achieve the commanded impact vector (i.e. elevation and
azimuth commands) within a defined tolerance. In LMT guidance mode, the weapon does not compute
separate In-Range and In-Zone IWL data. IR and IZ IWL data returned to the aircraft in LMT mode are
identical.
79
Boeing Report 15J0089
May 1, 2015
Note that under the Core Interface Protocol, the QRC logic defined in Table 8.10 is still applicable to
aircraft that have implemented the Full Laser Interface. If the aircraft sends commands to LJDAM that
activates one of these QRC modes, LJDAM guidance will respond according to the logic in Table 8.10. In
this case, LJDAM IWL does not correspond to the LJDAM guidance implementation, and is therefore
invalid. LJDAM IWL will return LBSLN IWL data to the aircraft if a QRC mode is activated, which is
overly optimistic of true LJDAM QRC capability. One unique mode not shown in Table 8.10 when full
laser interface is enabled is the use of impact angle commands of 67 and 82 with impact azimuth valid. If
this is commanded the weapon is initialized with a zero velocity bias. The purpose of this mode is to
provide a mechanism to override a TKS guidance command (in the event that an aircraft always commands
it).
The Rules of Thumb found in the appendices of this document must be used to employ LJDAM in Manual
Mode. Manual Mode is not supported under the UAI Interface protocol, and therefore operators will see
LJDAM LARs that accurately represents the guidance mode commanded.
80
Boeing Report 15J0089
May 1, 2015
In LMT guidance mode, the LAR will respond to target velocity inputs. The LMT LAR boundary will
move with target motion. While target motion is an order of magnitude less than the aircraft motion, target
motion can affect the time-dependent relationship between the aircraft and LAR. Figures 8.36 and 8.37
show the effect of target motion on the LARs returned. Figure 8.36 shows examples of how the LAR
changes position relative to the aircraft for various target headings. Figure 8.37 shows examples of how the
LAR changes position relative to the aircraft for various target speeds for a direct tail chase scenario.
81
Boeing Report 15J0089
May 1, 2015
Target Position
Target Heading = 0 deg
Target Heading = 90 deg
Target Heading = 180 deg
Target Heading = 270 deg
Figure 8.36 – LJDAM In Weapon LARs for Various Target Hdgs, Target Speed = 40 MPH
(20Kft HAT, 0.85M, Zero Wind, Sea Level)
Target Position
Target Speed = 0 mph
Target Speed = 30 mph
Target Speed = 60 mph
Target Speed = 90 mph
Figure 8.37 – LJDAM In Weapon LARs for Various Target Speeds, Tail Chase Scenario
(20Kft HAT, 0.85M, Zero Wind, Sea Level)
82
Boeing Report 15J0089
May 1, 2015
The time-dependent nature of moving target LARs necessitates a mechanism by which LAR data can be
represented as a future LAR location. There are two target location LAR types:
Current Target Location (CTL) LAR - based on the current target location
Propagated Target Location (PTL) LAR - based on the moving target location propagated to the
time of LAR entry
The PTL LAR Type is generated only in LMT Guidance Mode when the aircraft is outside of and
approaching the CTL LAR. A PTL LAR will be generated regardless of whether or not the aircraft heading
intersects the PTL LAR. An example is shown in Figure 8.38 below. At all other times, the CTL LAR type
is generated. Constant aircraft and target states (not including positions) during the approach to the PTL
LAR entry point will cause the PTL LAR to remain stationary. Once the aircraft enters the PTL LAR,
LJDAM will switch to computing a CTL LAR, which will move with target motion.
(+)
Propagated Target Location (PTL) Target
Target Motion
(-) (+)
Current Target Location (CTL) Target
PTL LAR
(-)
In addition to the LAR boundary moving with target motion, a dropout of data communication between the
weapon and the aircraft can cause LAR movement. If target speed dropouts occur, the LAR returned by the
weapon is a zero mile per hour target LAR during the dropout and a moving target LAR otherwise.
83
Boeing Report 15J0089
May 1, 2015
In LMT mode, the minimum impact angle used by LJDAM guidance and IWL is limited to 65 degrees. If
the commanded Impact Angle is less than 65 degrees, LJDAM guidance and IWL will utilize an Impact
Angle command of 65 degrees.
For LTKS and LMT modes, IWL data are considered to be accurate if the aircraft flight path angle is level
within ±5 degrees. If the aircraft is outside of this flight path angle window, IWL data will be returned as if
the aircraft flight path angle is at the +5 or -5 degree limit and IR/IZ status sent to the aircraft by the
weapon will always be False.
84
Boeing Report 15J0089
May 1, 2015
LMT
Guidance Mode LTKS
Slow Moving Targets Fast Moving Targets
Release Altitude
10 - 50kft 10 - 50kft 10 - 35kft
(HAT and MSL Limits)
Mach 0.65 - 1.3 Mach 0.65 - 1.3
Release Speed Mach 0.65 - 1.3
(Max Mach 0.90, MSL >45kft) (Max Mach 0.90, MSL >45kft)
Level only (Note 1) Level only (Note 1) Level only (Note 1)
Release Attitude
(+/-5 deg FPA) (+/-5 deg FPA) (+/-5 deg FPA)
Note 1: LJDAM IWL data provides level release information outside of +/-5 deg FPA, which
is Invalid. IR and IZ status (indication of ready to release) are set false under those conditions.
Note 2: LJDAM IWL will modify the impact angle command to the lower limit and provide
IWL data if the commanded impact angle is below the valid impact angle range (applies to
LTKS and LMT only).
Table 8.13 - Block 9 and Above LJDAM LTKS and LMT IWL Domain
In addition to the IWL domain parameters being met, the wind magnitude at the aircraft’s HAE release
altitude must be less than the MIL-STD-210C 95% wind limits which is shown in Table 8.14.
MSL Alt Wind Magnitude Limit Wind Magnitude Limit Wind Magnitude Limit
(ft) (fps) (MPH) (Knots)
-2000 61 42 36
3,280 98 67 58
6,560 112 76 66
13,100 148 101 88
19,700 190 130 113
26,200 246 168 146
32,800 292 199 173
39,400 312 213 185
45,900 266 181 158
52,500 226 181 158
85
Boeing Report 15J0089
May 1, 2015
The JDAM weapon falls ballistically until fin unlock. JDAM then increases its angle of attack in order to
self loft. The drag acting on the JDAM carries it aft of the host aircraft. The following rules are aimed at
providing adequate deconfliction.
Lowest Risk - Maintain or increase velocity and execute a single turn away from the target if a turn is
desired or required.
Avoid multiple turns, which may cause the aircraft to re-approach the bomb and degrade safe
separation. For example, delayed turns, such as “S turns”, back across the bomb trajectory after an
effective reduction in average groundspeed will increase the risk of recontact since JDAM can self-loft
above the release altitude for releases at airspeeds greater than 460 kts.
Do not execute a delayed turn back across the line-of-sight to the target.
Pull-ups are permitted before, during or after release. Pull-up is expected for dive release.
WARNING
In the event of a hung store occurring with an internal weapon carriage application, the tail assembly may
be warm to the touch due to the battery having been fired. Use care in handling to prevent personal injury.
NOTE
Upon power application, JDAM completes an initialization process that includes transfer of mission target
data and/or GPS crypto keys from the DTC/DTD/DTE to JDAM. With mission target data and/or GPS
crypto keys loaded, the JDAM tail kit is classified Secret and special handling is required. JDAM
implements a process, Classified Data Erase (CDE), which will zeroize the mission target data and/or GPS
crypto keys, downgrading the JDAM tail kit to unclassified. Once JDAM is powered on, it must be
assumed that mission target data and/or GPS crypto keys have been loaded into the JDAM tail kit. At any
time the JDAM weapon becomes inoperable, the tail kit must be considered classified and handled
appropriately. A positive indication that a satisfactory CDE has been performed is required before the tail
kit can be considered downgraded to unclassified. CDE can be initiated automatically upon JDAM power
shutdown or can be manually selected by the aircrew. The method for initiating CDE and verifying that a
satisfactory CDE has been completed is aircraft specific. When a JDAM weapon is returned after a
mission, it is the responsibility of the aircrew to verify that CDE has been satisfactorily completed before
aircraft shutdown. If this is not accomplished, the aircrew must annotate A/C Forms, AF Form 781, as
applicable and notify ground crew personnel that the JDAM is classified.
If circumstances dictate aircrew leave classified data in the JDAM Weapon as part of contingency
requirements, the A/C Forms should be annotated so ground crew personnel are aware weapons are
classified should the weapons be downloaded for maintenance action.
CDE can also be performed by munitions personnel using CMBRE. When notified by the aircrew that a
JDAM weapon is classified, munitions personnel can perform a CMBRE CDE which will provide positive
feedback that crypto data has been zeroized. If CDE on the aircraft or with CMBRE has not been
successfully accomplished, the JDAM tail kit must be stored and shipped as Secret Crypto material.
.
86
Boeing Report 15J0089
May 1, 2015
The JDAM weapon is handled in the same manner as the existing MK 84, BLU-109 and MK 82 (GBU-38
and GBU-54) general purpose and special purpose weapons currently in use. Using the existing emergency
procedures for those weapons would accomplish the same functions for the JDAM weapons. JDAM
weapons are jettisoned, if required, in the same manner as other existing general purpose weapons. The
only unique emergency procedure associated with the use of a JDAM weapon that is implemented for
GBU-31 and GBU-38 is that a crypto data erase (CDE) operation should be performed prior to jettison if
time allows.
Crypto keys are loaded to the host aircraft. The host aircraft then passes these keys to the JDAM as needed.
Should an emergency occur requiring a JDAM to be selectively jettisoned, the host aircraft may issue a
command to zeroize the keys which will cause the weapon to carry out the function (to do this the weapon
must be powered up). However, the aircraft may not delay the jettison process, waiting for confirmation
that the keys have been zeroized. Additionally, in the case of an emergency jettison, the host aircraft might
not command a key zeroization.
As indicated previously, baseline JDAM mission planning will be accomplished using the current
computerized mission planning system. However, for initial LJDAM fielding, it will be up to the aircrew to
manually plan their mission. In addition, for baseline JDAM, in some instances computerized mission
planning capabilities may not be available. The following guidelines have been established to assist the
effort required for manually planning a JDAM mission. Section 8.6.1 provides manual mission planning
guidelines for when the weapon is in GPS\INS, mode with no lasing. Section 8.6.2 provides guidelines
when the weapon is in lasing mode and being guided to the target by laser spot.
Due to the wide range of available release parameters typically associated with a JDAM mission, a
minimum subset of conditions has been established and should be used in order to simplify this process.
These conditions are summarized in Table 8.16. Be advised that there are two sets of MK-82 footprints
depending on whether the Slick ADE or the Centered ADE is used (see JDAM LAR section). The
following steps provide an example of how to manually plan a JDAM mission:
1. Determine the target characteristics. These characteristics are based on an assessment of reconnaissance
data and/or intelligence estimates and a review of aeronautical charts or topographical maps containing the
target area. The results of this research should yield:
4. Determine minimum weapon impact conditions. These parameters will vary depending on the target
characteristics and desired weapon effect. For example:
Default the Target Impact Azimuth to 0 relative to true north (0º = Invalid, not used).
87
Boeing Report 15J0089
May 1, 2015
5. Determine weather conditions at target area from forecasted weather data. This information is for
aircrew flight planning purposes to assist in determination of a desired delivery mode. Weather conditions
at the target area have little to no bearing on the JDAM weapon, however, the LAR will be impacted by
winds at the target and should be taken into account when mission planning.
6. Determine desired delivery mode and associated airspeeds, in knots true airspeed (KTAS), from these
three options:
7. Determine desired egress course, altitude and maneuvers required, based on a review of an aeronautical
chart covering the target area.
8. Determine desired release altitudes. Refer to Table 8.15 for possible choices. Altitude references are in
MSL unless specifically noted otherwise.
9. Based on the desired release parameters determined, refer to Table 8.15 and locate the corresponding
footprint figure. Go to that figure, locate the related footprint and identify the crossrange and downrange
boundaries.
10. Identify a weapon release point that will result in the target area being within the boundaries of the
footprint area. If the target lies on the outer edge of a footprint area, the release parameters can be altered
slightly to select a footprint, which results in the target being well inside the boundaries. In many cases a
change in delivery airspeed is all that is required.
11. If applicable to the mission, identify any required Joint Programmable Fuze (JPF) parameters. JPF
Parameters include:
Fuze Mode Selection
Arm Time from Release
Fuze Function Time from Impact
12. Once the planning has been completed, load the applicable mission data into the host aircraft on board
computer and the JDAM weapon mission computer.
88
Boeing Report 15J0089
May 1, 2015
0.50
65 deg 0.60
+/-8 deg 0.70
0.80
0.90
1.00
1.10
0.40
25 deg 0.50
+/-8 deg 0.60
20,000 ft. 0.70
0.80 Figure 8.40
0.90
65 deg 1.00
+/-8 deg 1.10
1.20
25 deg 0.50
+/-8 deg 0.60
0.70
30,000 ft. 0.80 Figure 8.41
0.90
1.00
65 deg 1.10
+/-8 deg 1.20
Table 8.15 - JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
89
Boeing Report 15J0089
May 1, 2015
25 +/-8 deg
0.70
50,000 ft. 65 +/-8 deg 0.80 Figure 8.43
0.90
25 +/-8 deg
Loft 2058 ft.
3007 ft. 0.90 Figure 8.44
4156 ft. 65 +/-8 deg
25 +/-8 deg
Dive Figure 8.45
65 +/-8 deg
Command
Azimuth 25 +/-8 deg Figure 8.47
25 +/-8 deg
Target 25,000 ft. AGL
Altitude 30,000 ft. AGL 65 +/-8 deg Figure 8.48
25 +/-8 deg
Winds 30,000 ft. Figure 8.49
(59 kts) 65 +/-8 deg Figure 8.50
(119 kts)
Table 8.15 - JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(cont.)
90
Boeing Report 15J0089
May 1, 2015
0.60
65 deg 0.70
+/-8 deg 0.80
0.90
1.00
1.10
0.40
25 deg 0.50
+/-8 deg 0.60
20,000 ft. 0.70
0.80 Figure 8.52
0.90
65 deg 1.00
+/-8 deg 1.10
1.20
25 deg 0.50
+/-8 deg 0.60
0.70
30,000 ft. 0.80 Figure 8.53
0.90
1.00
65 deg 1.10
+/-8 deg 1.20
Table 8.15 JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(cont.)
91
Boeing Report 15J0089
May 1, 2015
25 +/-8 deg
0.70
50,000 ft. 65 +/-8 deg 0.80 Figure 8.55
0.90
25 +/-8 deg
Loft 2058 ft.
3007 ft. 0.90 Figure 8.56
4156 ft. 65 +/-8 deg
25 +/-8 deg
Dive Figure 8.57
65 +/-8 deg
Command
Azimuth 25 +/-8 deg Figure 8.59
25 +/-8 deg
Target 25,000 ft. AGL
Altitude 30,000 ft. AGL 65 +/-8 deg Figure 8.60
25 +/-8 deg
Winds 30,000 ft. Figure 8.61
(59 kts) 65 +/-8 deg Figure 8.62
(119 kts)
Table 8.15 JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(cont.)
92
Boeing Report 15J0089
May 1, 2015
0.50
65 deg 0.60
+/-8 deg 0.70
0.80
0.90
1.00
1.10
0.40
25 deg 0.50
+/-8 deg 0.60
20,000 ft. 0.70
0.80 Figure 8.64
0.90
65 deg 1.00
+/-8 deg 1.10
1.20
25 deg 0.50
+/-8 deg 0.60
0.70
30,000 ft. 0.80 Figure 8.65
0.90
1.00
65 deg 1.10
+/-8 deg 1.20
Table 8.15 - JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(Cont.)
93
Boeing Report 15J0089
May 1, 2015
25 +/-8 deg
0.70
50,000 ft. 65 +/-8 deg 0.80 Figure 8.67
0.90
25 +/-8 deg
Loft 2058 ft.
3007 ft. 0.90 Figure 8.68
4156 ft. 65 +/-8 deg
25 +/-8 deg
Dive Figure 8.69
65 +/-8 deg
Command
Azimuth 25 +/-8 deg Figure 8.71
25 +/-8 deg
Target 25,000 ft. AGL
Altitude 30,000 ft. AGL 65 +/-8 deg Figure 8.72
25 +/-8 deg
Winds 30,000 ft. Figure 8.73
(59 kts) 65 +/-8 deg Figure 8.74
(119 kts)
Table 8.15 - JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(cont.)
94
Boeing Report 15J0089
May 1, 2015
0.50
65 deg 0.60
+/-8 deg 0.70
0.80
0.90
1.00
1.10
0.40
25 deg 0.50
+/-8 deg 0.60
20,000 ft. 0.70
0.80 Figure 8.76
0.90
65 deg 1.00
+/-8 deg 1.10
1.20
25 deg 0.50
+/-8 deg 0.60
0.70
30,000 ft. 0.80 Figure 8.77
0.90
1.00
65 deg 1.10
+/-8 deg 1.20
Table 8.15 - JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(cont.)
95
Boeing Report 15J0089
May 1, 2015
25 +/-8 deg
0.70
50,000 ft. 65 +/-8 deg 0.80 Figure 8.79
0.90
25 +/-8 deg
Loft 2058 ft.
3007 ft. 0.90 Figure 8.80
4156 ft. 65 +/-8 deg
25 +/-8 deg
Dive Figure 8.81
65 +/-8 deg
Command
Azimuth 25 +/-8 deg Figure 8.83
25 +/-8 deg
Target 25,000 ft. AGL
Altitude 30,000 ft. AGL 65 +/-8 deg Figure 8.84
25 +/-8 deg
Winds 30,000 ft. Figure 8.85
(59 kts) 65 +/-8 deg Figure 8.86
(119 kts)
Table 8.15 - JDAM GBU-31 Series; GBU-38 Series Release Parameters for Manual Mission Planning
(cont.)
96
Boeing Report 15J0089
May 1, 2015
97
Boeing Report 15J0089
May 1, 2015
98
Boeing Report 15J0089
May 1, 2015
99
Boeing Report 15J0089
May 1, 2015
100
Boeing Report 15J0089
May 1, 2015
101
Boeing Report 15J0089
May 1, 2015
102
Boeing Report 15J0089
May 1, 2015
103
Boeing Report 15J0089
May 1, 2015
104
Boeing Report 15J0089
May 1, 2015
105
Boeing Report 15J0089
May 1, 2015
106
Boeing Report 15J0089
May 1, 2015
107
Boeing Report 15J0089
May 1, 2015
108
Boeing Report 15J0089
May 1, 2015
109
Boeing Report 15J0089
May 1, 2015
110
Boeing Report 15J0089
May 1, 2015
111
Boeing Report 15J0089
May 1, 2015
112
Boeing Report 15J0089
May 1, 2015
113
Boeing Report 15J0089
May 1, 2015
114
Boeing Report 15J0089
May 1, 2015
115
Boeing Report 15J0089
May 1, 2015
Figure 8.58 GBU-31 Series With & Without Impact Constraints on Delivery
116
Boeing Report 15J0089
May 1, 2015
117
Boeing Report 15J0089
May 1, 2015
118
Boeing Report 15J0089
May 1, 2015
119
Boeing Report 15J0089
May 1, 2015
120
Boeing Report 15J0089
May 1, 2015
Figure 8.63 - GBU-38 Series (Slick Warhead/Slick ADE) Level Delivery - 10Kft
121
Boeing Report 15J0089
May 1, 2015
Figure 8.64 - GBU-38 Series (Slick Warhead/Slick ADE) Level Delivery - 20Kft
122
Boeing Report 15J0089
May 1, 2015
Figure 8.65 - GBU-38 Series (Slick Warhead/Slick ADE) Level Delivery - 30Kft
123
Boeing Report 15J0089
May 1, 2015
Figure 8.66 - GBU-38 Series (Slick Warhead/Slick ADE) Level Delivery - 40Kft
124
Boeing Report 15J0089
May 1, 2015
Figure 8.67 - GBU-38 Series (Slick Warhead/Slick ADE) Level Delivery - 50Kft
125
Boeing Report 15J0089
May 1, 2015
126
Boeing Report 15J0089
May 1, 2015
127
Boeing Report 15J0089
May 1, 2015
Figure 8.70 - GBU-38 Series (Slick Warhead/Slick ADE) With & Without Impact Constraints on
Delivery
128
Boeing Report 15J0089
May 1, 2015
Figure 8.71 - GBU-38 Series (Slick Warhead/Slick ADE) Commanded Azimuth Delivery
129
Boeing Report 15J0089
May 1, 2015
Figure 8.72 - GBU-38 Series (Slick Warhead/Slick ADE) Target Altitude Delivery
130
Boeing Report 15J0089
May 1, 2015
Figure 8.73 - GBU-38 Series (Slick Warhead/Slick ADE) Winds on Delivery – 59 kts
131
Boeing Report 15J0089
May 1, 2015
Figure 8.74 - GBU-38 Series (Slick Warhead/Slick ADE) Winds on Delivery – 119kts
132
Boeing Report 15J0089
May 1, 2015
Figure 8.75 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Level Delivery - 10Kft
133
Boeing Report 15J0089
May 1, 2015
Figure 8.76 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Level Delivery - 20Kft
134
Boeing Report 15J0089
May 1, 2015
Figure 8.77 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Level Delivery - 30Kft
135
Boeing Report 15J0089
May 1, 2015
Figure 8.78 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Level Delivery - 40Kft
136
Boeing Report 15J0089
May 1, 2015
Figure 8.79 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Level Delivery - 50Kft
137
Boeing Report 15J0089
May 1, 2015
Figure 8.80 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Loft Delivery
138
Boeing Report 15J0089
May 1, 2015
Figure 8.81 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Dive Delivery
139
Boeing Report 15J0089
May 1, 2015
Figure 8.82 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) With & Without Impact
Constraints on Delivery
140
Boeing Report 15J0089
May 1, 2015
Figure 8.83 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Commanded Azimuth
Delivery
141
Boeing Report 15J0089
May 1, 2015
Figure 8.84 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Target Altitude Delivery
142
Boeing Report 15J0089
May 1, 2015
Figure 8.85 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Winds on Delivery - 59kts
143
Boeing Report 15J0089
May 1, 2015
Figure 8.86 - GBU-38 Series (Slick or Thermal Warhead/Centered ADE) Winds on Delivery - 119 kts
144
Boeing Report 15J0089
May 1, 2015
Alternate warheads to the “baseline” JDAM warheads (i.e. GBU-31 and 38) have been evaluated for
compatibility with the JDAM guidance sets. Beyond aircraft integration studies such as loads and weapon
separation, the warheads are evaluated for autopilot compatibility and impacts to the heritage JDAM LAR
performance for that class warhead (i.e. 500 lb or 2000 lb). Some alternate warheads may be considered
compatible with a JDAM tailkit however the LAR performance can be significantly altered. In such cases
and where requested, sample manual mission planning footprints will be presented.
Mission planning procedures in GPS\INS mode for alternate warheads will be identical to the steps used to
employ JDAM using baseline series warheads. As other alternate warheads are integrated with JDAM
tailkits, sample footprints may be placed here in this section as required.
For Block 8 LJDAM versions and later, the Laser JDAM OFP contains In-Weapon-LAR (IWL) models
that represent the highest fidelity LAR based upon the current aircraft release conditions, guidance
commands and the target parameters. Aircraft that have the full laser functionality in their aircraft interface
will be able to receive continuously updating LARs in the cockpit so long as they are within the range of
the IWL database. For aircraft that have not implemented the full laser functionality in their interface, or
that do not implement IWL, it will be up to the aircrew to manually plan their mission.
This supplementary data in this section and the following Appendices offers several forms of information
to help an aircrew understand acceptable conditions to employ Laser JDAM successfully including:
derating guidelines for employing against stationary targets using MK-82 IWL, energy capability curves,
Rule of Thumb (ROT) Tables and footprint examples.
The derating guidelines in Section 8.6.2.1 provide some guidance for employing LJDAM against stationary
targets for platforms that use or have access to MK-82 IWL models. Following Section 8 are Appendices
A, B and C that contain the LJDAM employment and performance data. Table 8.16 provides a top level
definition of what data sets are in each appendix.
Appendices A and B contain the source data for slick ADE. The ground range and slant range ROTs are
separated into different appendices to avoid confusion. Energy capability curves and sample footprints are
identical in Appendix A and B so that each section can stand alone without need for cross-referencing.
Information about each ROT format can be found in the respective appendix.
Each appendix contains energy capability curves, ROT tables and sample footprints. The energy capability
curves are plots that provide a top level picture of where ROTs exist in the release envelope for a variety of
target sets and winds conditions. They do not provide release distances, but are simply meant to help
understand the minimum energy required in release airspeed and altitude to use the ROTs for a specific
target set. As mentioned, ROTs are ground or slant range release distances to a target for a given release
condition that should result in the weapon meeting the accuracy requirements. It should be understood that
ROTs do not represent the full capability of the weapon system, rather, they are greatly simplified release
Points that are valid for a wide variety of conditions (wind magnitudes/headings and target
speeds/heading).
145
Boeing Report 15J0089
May 1, 2015
Laser JDAM LARs for a specific release condition represents the weapon systems full capability. Each
Appendix shows a set of Laser JDAM footprints for fixed and moving targets. Release altitudes are defined
as height above the target (HAT) and all scenarios are presented for straight and level aircraft approach. All
footprints assume a 4 km acquisition range from the target and continuous lasing to the target. The
footprints assume no target heading error and are generated using the ADE shown in Table 8.16. In the case
of Appendix A, the footprints are valid for either slick or thermal warheads. The footprints will represent
weapon performance for final impact angles between 45-90º.
Figure 8.87 provides an example of the general derating scheme. For manual mission planning of the
GBU-54 LJDAM, the derating factors shown in Table 8.17 should be applied to the GBU-38 MK-82 LAR
as a percentage of cross-sectional distance in both crossrange and downrange to obtain valid LARs for the
GBU-54 LJDAM. Note that the minimum range derating is only required for launches above 25Kft HAT.
Nominal
Max DR Derate 30 %
GBU-38 IWL DR of DR Cross-section
Derated GBU-38
LAR for GBU -54
DR Cross-section
CR Cross-section CR
Figure 8.87 – General Derating of a GBU-38 JDAM LAR for GBU-54 LJDAM
146
Boeing Report 15J0089
May 1, 2015
Range Reduction
Minimum Down Range 10%*
Maximum Down Range 30%
Cross Range 25%
* Minimum Down Range Derating is only required for launches above 25 kft Height-Above-Target (HAT)
Table 8.17 - Block 08 and Above GBU-54 LJDAM De-Ratings for Stationary Targets (Applied to
Baseline GBU-38 LJDAM LAR)
Specific footprints and ROTs are provided for manual mission planning in the appendices as defined in
Table 8.16. The following plots provide a sample of the effects of day type, wind parameters, and target
altitude.
Figure 8.88 - GBU-54 Stationary Target Day Type Comparison, Cold / Polar
147
Boeing Report 15J0089
May 1, 2015
Figure 8.89 - GBU-54 Stationary Target Day Type Comparison, Hot / Tropical
Figure 8.90 - GBU-54 Stationary Target Wind Speed Variation, 0 deg Winds
148
Boeing Report 15J0089
May 1, 2015
Figure 8.91- GBU-54 Stationary Target Wind Speed Variation, 90 deg Winds
Figure 8.92 - GBU-54 Stationary Target Wind Speed Variation, 180 deg Winds
149
Boeing Report 15J0089
May 1, 2015
Figure 8.93 - GBU-54 Stationary Target Wind Speed Variation, 270 deg Winds
Figure 8.94 - GBU-54 Stationary Target Wind Direction Variation, 100 kt Winds
150
Boeing Report 15J0089
May 1, 2015
Figure 8.95 - GBU-54 Stationary Target, Target Altitude Variation, No Velocity Bias, HAT = 20 kft,
Impact Angle = 70 deg, TALT = 0, 2, 5 and 10 kft
Figure 8.96 - GBU-54 Stationary Target, Target Altitude Variation, No Velocity Bias, HAT = 30 kft,
Impact Angle = 70 deg, TALT = 0, 2, 5 and 10 kft
151
Boeing Report 15J0089
May 1, 2015
The energy capability curves provide a quick reference to help select release conditions that will ensure
there is a ROT available to pursue a specific target. The curves show the minimum energy (as a
combination of Mach and height above target) required to successfully engage a specific target speed and
target altitude. There are multiple curves on each plot and each represents a maximum wind limit in knots.
The legend describes the target altitude and maximum allowable wind magnitude. The curves are valid for
winds from any direction. In each plot, a valid ROT should exist for any Mach and altitude that is above
and to the right of the applicable curve as shown in Figure A.1. Mach and altitude combinations that are
below and to the left of the curve will not result in a valid ROT due to a combination of things: the
constraints of the ROT table (i.e., Omni-directional capability), and limited energy at release to satisfy all
requirements in the tables (i.e. meeting accuracy requirements in all specified wind conditions, target
directions, headings, etc). Knowing the maximum winds and target altitude for a specific mission should
help narrow down the minimum release speeds and altitudes required to engage either slow (0-40MPH) or
fast (40-70 MPH) moving targets.
The first three energy capability plots, Figures A.1-A3 show where ROTs exist at all release altitudes for
targets moving 0-40MPH in any direction (Omni-directional). Figures A.1, A.2 and A.3 show the results
for 0, 5 and 10 Kft MSL target altitudes, respectively. Figures A.4-A.6 show where ROTs exist at release
altitudes of 20Kft HAT and above against targets moving 40 to 70 MPH. Note fast mover ROTs are
restricted to a tail-chase constraint of +/- 45 deg, that is, the aircraft heading must be within +/- 45 degrees
of the target heading. Figures A.4, A.5 and A.6 also show results for 0, 5 and 10 Kft MSL target altitudes
respectively. Figures A.7 through A.9 show where ROTs exist at release altitudes of 15Kft HAT and below
for targets moving 40 to 50 MPH. Figures A.7, A.8 and A.9 also show results for 0, 5 and 10 Kft MSL
target altitudes respectively.
Figure A.1 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
0 Kft MSL Target Altitude
152
Boeing Report 15J0089
May 1, 2015
Figure A.2 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
5 Kft MSL Target Altitude
Figure A.3 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
10 Kft MSL Target Altitude
153
Boeing Report 15J0089
May 1, 2015
Figure A.4 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º
0 Kft MSL Target Altitude
Figure A.5 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º
5 Kft MSL Target Altitude
154
Boeing Report 15J0089
May 1, 2015
Figure A.6 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º
10 Kft MSL Target Altitude
Figure A.7 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
0 Kft MSL Target Altitude
155
Boeing Report 15J0089
May 1, 2015
Figure A.8 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
5 Kft MSL Target Altitude
Figure A.9 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
10 Kft MSL Target Altitude
156
Boeing Report 15J0089
May 1, 2015
ROT tables were tailored to address operator feedback on data organization. The general goal was to reduce
the amount of real-time decision making required during run-in to successfully employ the weapon.
Therefore all ROT tables are broken out for a maximum wind and are independent of wind direction. Once
a maximum wind for the day has been established, an appropriate table can be selected prior to the mission
and winds will not need real-time consideration. Tables are available that address slow moving (0-40 MPH)
and fast moving (40-70 MPH) targets. Block 8 (and later) software improvements have made it possible to
compute Omni-directional ROTs for slow moving targets (0-40MPH). Thus for slow movers, target
heading need not be a real-time consideration. ROTs for fast moving targets (40 -70 MPH) are still
restricted to a ±45º tail chase condition.
ROT results shown below are then valid for the maximum wind and target speeds listed at the top of each
table. They are independent of wind direction. The appropriate table for the mission is selected based on the
expected winds that day and expected target speeds to engage. Each table provides release ground range
distances for release altitudes of 10, 12.5, 15, 20, 25, 30 and 35 Kft HAT and for Mach points of 0.70, 0.75,
0.80, 0.85, 0.90 and 0.95. For each altitude and Mach combination, a release ground range distance is listed
for target altitudes of 0, 5 and 10 Kft MSL. No ROTs were provided for release altitudes above 35 Kft
MSL. Release altitudes at 40 Kft and above were not identified as high priority and data generation was
concentrated on lower altitude employment.
Under the target altitude columns, there is a release ground range distance to target with a tolerance
denoted by the symbol “±”. So for example a release ground range distance of 3 nmi ± 1 nmi would
represent a 2 nmi long ROT box that is valid from 2 to 4 nmi downrange to the target. For a ROT to be
considered valid it should have a minimum of ±0.3 nmi of depth. Cases where the ROT depth is less are
provided in the table, but shown in red to help with interpolation between ROTs. Cases where no ROT
exists for that condition show up as “NoROT” in the table. The cross range tolerance on the ROT box is a
minimum of ± 0.3 nmi wide. The ROT models are designed for a weapon accuracy of 5m CEP for 0-
40MPH targets and 6m CEP for 40-70 MPH targets. They also assume that the achieved weapon impact
angle is 30-90º. All ground range release distances are only valid for the impact angle and impact azimuth
commands listed in the third and fourth columns. Note that the ROT boxes (i.e. the ROT +/- the tolerance)
for each case represents the un-conservative, maximized window for which the weapon can be employed.
Similar to JDAM baseline LARs, for the greatest probability of success it is advised to release as close to
the ROT center as possible.
The following two sections, A.2.1-A.2.2, show the generalized ROT tables and an additional set of tables
that are focused on special employment circumstances. Section A.2.1 shows the generalized ROT tables for
slow (0-40 MPH) and fast (40-70 MPH) moving targets. Section A.2.2 shows ROT tables for employment
against very slow movers (0-10 MPH) and is intended to supplement the general ROT tables in order to
open up capability for this specific condition. Section A.2.3 shows ROT tables for LJDAM employment at
altitudes below 10 Kft HAT and at negative flight path angles.
A.2.1 Slow (0-40 MPH) and Fast (40-70 MPH) Mover Ground Range ROT
Tables
For the slow mover tables (0-40 MPH), the impact angle command has two settings depending on the
estimated target speed. If the target is moving very slow, approximately 0-20 MPH, the ROT can be used
without passing a velocity bias to the weapon and impact angle commands of 70-90º can be used. Impact
azimuth command is not required and if not specifically needed, should be set as invalid. If a target is
moving in the range of 20-40 MPH, the ROT can be used by commanding an impact angle of 68º or 83º,
which passes a 40 MPH velocity bias to the weapon. In this case the impact azimuth command should be
valid and used to specify the target heading at release (See Table 8.9 – Block 9 Manual Mode Velocity Bias
Logic Summary).
157
Boeing Report 15J0089
May 1, 2015
There is no significant change in weapon performance at a target speed breakpoints found in the table and
some degree of overlap is acceptable. For example at 20 MPH, some overlap exists where either impact
angle command can be used, that is, one that specifies no velocity bias (70-90º) or one that specifies a 40
MPH velocity bias (68º or 83º). When choosing the appropriate impact angle command and velocity bias,
the weapon performance is optimized by passing the weapon the closest approximation possible to the
target’s true speed. Each ground range release distance shown in the table is valid for either case (i.e., either
using 70-90º impact angle command with an invalid azimuth command for 0-20 MPH targets or a 68º/83º
impact angle command with a valid azimuth command defining the target heading for 20-40 MPH targets).
Similarly for the fast mover tables (40-70 MPH) at high HAT release conditions of 20-35Kft HAT, there
are two settings for impact angle command. For targets moving 40-60 MPH, the ROTs can be used by
commanding an impact angle of 68º or 83º (40 MPH bias) and for targets moving 60-70 MPH, the ROTs
can be used by commanding an impact angle of 69º or 84º (60 MPH bias). In either case, the impact
azimuth command should again be valid and used to specify the target heading at release.
For low HAT release conditions of 10-15Kft, the ROTs in the fast mover table are only provided for target
speeds up to 50 MPH. At low release altitudes performance degrades against 50-70 MPH targets. The ROT
capability is much greater by only engaging targets up to 50 MPH at this altitude. For these low HAT
conditions engaging target speeds of 40-50 MPH, the ROTs can be used by commanding an impact angle
of 68º or 83º (40 MPH bias) and specifying target heading via the azimuth command.
Note that all downrange distances shown are distances to the target at weapon separation, not weapon
pickle. An additional downrange increment should be added based on the specific aircraft pickle duration
and aircraft inertial speed at release.
Tables A.1 - A.5 provide the Rules of Thumb for Omni-directional targets of speeds between 0-40 MPH for
wind limits of 20, 40, 60, 80, and 100 knots respectively. Tables A.6 - A.10 provide the Rules of Thumb for
targets of speeds between 40-70 MPH, subject to a ±45º tail chase condition, for wind limits of 20, 40, 60,
80, and 100 knots respectively.
To reduce the amount of real-time lookup aircrews must accomplish, the intent here is that they select the
appropriate table from below prior to the mission based on winds that day and anticipated target speeds.
For example if winds are 30-40 knots and target speeds are expected to be 0-40 MPH, Table A.2 would be
selected as that data is for slow movers and valid up to maximum wind speeds of 40 knots. (As noted, all
the ROT tables below are independent of wind direction).
Once the table is selected the aircrew can mission plan their release altitude and airspeed based upon the
capability of the aircraft and weapon at the expected target altitude. For slow movers, the operator should
only have to check the release ground range and set the impact angle commands to employ the weapon. To
engage fast moving targets the aircraft would also need to be in a tail chase condition.
In the unique case where the target is fixed or moving approximately 20 MPH or slower, it is possible to set
the impact angle command anywhere between 70-90º prior to run on the target (bearing in mind that impact
azimuth command should be invalid for impact angle commands of 83º and 84º to inhibit sending a
velocity bias to the weapon). Then there is only one real-time parameter to consider - the correct release
ground range distance to the target.
158
Boeing Report 15J0089
May 1, 2015
Table A.1- LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 20 Knots
(Slick ADE, 0.70-0.95M)
159
Boeing Report 15J0089
May 1, 2015
Table A.2 – LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 40
Knots (Slick ADE, 0.70-0.95M)
160
Boeing Report 15J0089
May 1, 2015
Table A.3 – LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph for Winds
Up To 60 Knots (Slick ADE, 0.70-0.95M)
161
Boeing Report 15J0089
May 1, 2015
Table A.4 - LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 80
Knots (Slick ADE, 0.70-0.95M)
162
Boeing Report 15J0089
May 1, 2015
Table A.5 - LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 100
Knots (Slick ADE, 0.70-0.95M)
163
Boeing Report 15J0089
May 1, 2015
0.80 68° or 83° (40-60 MPH) Req 4.8 3.9 4.9 3.5 44 - 89
30
0.85 69° or 84° (60-70 MPH) Req 4.8 4.4 5.1 3.6 43 - 92
0.90 5.2 4.2 5.5 3.6 42 - 93
0.95 5.7 4.4 5.9 3.9 41 - 98
0.70 3.9 2.7 4.0 2.3 3.9 1.9 39 - 74
0.75 4.2 2.8 4.3 2.6 4.2 2.1 39 - 77
0.80 68° or 83° (40-60 MPH) Req 4.3 3.1 4.5 2.8 4.4 2.3 38 - 80
25
0.85 69° or 84° (60-70 MPH) Req 4.6 3.4 4.5 3.1 4.6 2.5 38 - 84
0.90 4.7 3.7 4.9 3.1 4.9 2.6 37 - 86
0.95 5.2 3.5 5.4 3.3 5.4 2.8 36 - 88
0.70 3.4 1.9 3.5 1.7 3.4 1.3 33 - 62
0.75 3.7 2.0 3.8 1.8 3.7 1.5 33 - 65
0.80 68° or 83° (40-60 MPH) Req 3.9 2.2 3.9 2.0 3.9 1.7 32 - 68
20
0.85 69° or 84° (60-70 MPH) Req 4.0 2.4 4.1 2.2 4.0 2.0 32 - 71
0.90 4.2 2.5 4.3 2.6 4.2 1.9 31 - 74
0.95 4.5 2.7 4.6 2.5 4.7 2.3 30 - 78
0.70 3.1 1.5 3.2 1.4 3.2 1.1 28 - 56
0.75 3.4 1.7 3.4 1.5 3.4 1.3 27 - 61
0.80 3.6 1.9 3.7 1.7 3.7 1.5 27 - 65
15 68° or 83° (40-50 MPH) Req
0.85 3.8 2.0 3.9 1.9 3.8 1.7 26 - 68
0.90 4.1 2.2 4.1 2.1 4.0 1.9 26 - 71
0.95 4.3 2.3 4.4 2.2 4.4 2.0 25 - 74
0.70 2.9 1.1 2.8 1.0 2.8 0.7 25 - 49
0.75 3.1 1.3 3.1 1.1 3.1 0.9 24 - 53
0.80 3.2 1.5 3.4 1.3 3.3 1.1 24 - 57
12.5 68° or 83° (40-50 MPH) Req
0.85 3.5 1.6 3.5 1.5 3.5 1.3 23 - 61
0.90 3.6 1.8 3.8 1.7 3.7 1.6 23 - 63
0.95 4.0 1.9 4.1 1.8 4.1 1.7 22 - 68
0.70 2.6 0.7 2.5 0.5 NoRot N/A 23 - 39
0.75 2.8 0.9 2.8 0.7 2.6 0.2 22 - 43
0.80 2.9 1.1 3.0 0.9 2.8 0.6 21 - 46
10 68° or 83° (40-50 MPH) Req
0.85 3.1 1.2 3.2 1.1 3.2 0.8 21 - 50
0.90 3.4 1.3 3.4 1.3 3.4 1.1 21 - 56
0.95 3.6 1.5 3.6 1.4 3.6 1.3 21 - 60
Table A.6 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 20
Knots (Slick ADE, 0.70-0.95M)
164
Boeing Report 15J0089
May 1, 2015
0.80 68° or 83° (40-60 MPH) Req 4.6 3.8 4.6 3.2 43 - 89
30
0.85 69° or 84° (60-70 MPH) Req 4.5 4.0 4.9 3.3 42 - 89
0.90 5.0 4.0 5.2 3.3 42 - 93
0.95 5.3 4.0 5.7 3.7 41 - 94
0.70 3.7 2.4 3.8 2.1 3.7 1.6 39 - 72
0.75 4.0 2.6 4.0 2.2 4.0 1.7 39 - 76
0.80 68° or 83° (40-60 MPH) Req 4.1 2.8 4.3 2.5 4.2 2.1 38 - 78
25
0.85 69° or 84° (60-70 MPH) Req 4.4 3.0 4.2 2.8 4.4 2.2 38 - 82
0.90 4.6 3.4 4.7 2.9 4.7 2.2 36 - 86
0.95 5.0 3.3 5.2 2.9 5.1 2.6 36 - 87
0.70 3.1 1.5 3.2 1.3 3.2 0.9 33 - 60
0.75 3.4 1.7 3.5 1.5 3.5 1.2 33 - 62
0.80 68° or 83° (40-60 MPH) Req 3.5 1.8 3.7 1.6 3.7 1.4 32 - 64
20
0.85 69° or 84° (60-70 MPH) Req 3.7 2.0 3.9 2.0 3.7 1.5 31 - 68
0.90 4.0 2.2 4.0 2.2 4.1 1.6 31 - 72
0.95 4.2 2.2 4.4 2.1 4.4 1.9 30 - 74
0.70 2.9 1.3 3.0 1.0 3.0 0.8 28 - 54
0.75 3.3 1.4 3.2 1.2 3.2 1.0 27 - 59
0.80 3.4 1.5 3.4 1.4 3.4 1.1 27 - 61
15 68° or 83° (40-50 MPH) Req
0.85 3.5 1.7 3.7 1.6 3.6 1.4 26 - 64
0.90 3.8 1.9 3.9 1.8 3.7 1.6 26 - 69
0.95 4.1 2.0 4.1 1.9 4.2 1.8 25 - 72
0.70 2.7 0.9 2.7 0.6 2.7 0.5 25 - 47
0.75 2.9 1.0 3.0 0.9 2.9 0.7 24 - 50
0.80 3.1 1.2 3.2 1.0 3.2 0.9 24 - 54
12.5 68° or 83° (40-50 MPH) Req
0.85 3.2 1.3 3.2 1.2 3.3 1.1 23 - 58
0.90 3.3 1.5 3.6 1.4 3.5 1.3 23 - 61
0.95 3.7 1.6 3.8 1.5 3.8 1.4 22 - 65
0.70 2.3 0.4 NoRot N/A NoRot N/A 22 - 32
0.75 2.5 0.6 2.5 0.3 NoRot N/A 22 - 35
0.80 2.7 0.8 2.7 0.6 NoRot N/A 21 - 39
10 68° or 83° (40-50 MPH) Req
0.85 2.9 0.9 3.0 0.8 2.9 0.5 21 - 42
0.90 3.2 1.1 3.2 1.0 3.2 0.8 21 - 52
0.95 3.4 1.2 3.5 1.1 3.4 1.0 21 - 54
Table A.7 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 40
Knots (Slick ADE, 0.70-0.95M)
165
Boeing Report 15J0089
May 1, 2015
0.80 68° or 83° (40-60 MPH) Req 4.3 3.4 4.6 2.6 44 - 86
30
0.85 69° or 84° (60-70 MPH) Req 4.5 3.7 4.9 2.8 42 - 89
0.90 5.0 3.4 5.2 2.8 41 - 90
0.95 5.2 3.7 5.5 3.1 41 - 93
0.70 3.5 2.1 3.6 1.6 3.6 1.3 39 - 69
0.75 3.7 2.2 3.8 1.8 3.8 1.4 39 - 71
0.80 68° or 83° (40-60 MPH) Req 4.0 2.1 4.1 2.3 4.0 1.7 38 - 73
25
0.85 69° or 84° (60-70 MPH) Req 4.0 2.7 4.1 2.3 4.2 1.7 38 - 79
0.90 4.4 3.0 4.4 2.4 4.5 1.8 36 - 83
0.95 4.8 2.9 4.9 2.6 4.9 2.1 36 - 85
0.70 2.8 1.0 3.0 0.9 3.0 0.5 33 - 56
0.75 3.0 1.1 3.2 1.1 3.2 0.7 33 - 58
0.80 68° or 83° (40-60 MPH) Req 3.1 1.3 3.5 1.3 3.4 1.1 32 - 60
20
0.85 69° or 84° (60-70 MPH) Req 3.4 1.5 3.5 1.5 3.6 1.2 31 - 63
0.90 3.6 1.7 3.7 1.7 3.8 1.2 31 - 67
0.95 3.7 1.7 4.1 1.6 4.3 1.5 30 - 67
0.70 2.8 0.9 2.8 0.7 2.8 0.4 28 - 51
0.75 3.0 1.1 3.0 0.9 3.1 0.7 27 - 56
0.80 3.2 1.3 3.2 1.1 3.3 0.9 27 - 60
15 68° or 83° (40-50 MPH) Req
0.85 3.3 1.4 3.3 1.3 3.4 1.1 26 - 62
0.90 3.4 1.5 3.5 1.5 3.7 1.3 26 - 64
0.95 3.8 1.6 4.0 1.6 3.9 1.4 25 - 68
0.70 2.4 0.5 2.5 0.3 NoRot N/A 24 - 39
0.75 2.7 0.7 2.6 0.5 2.6 0.2 24 - 45
0.80 2.8 0.8 3.0 0.7 2.9 0.5 23 - 47
12.5 68° or 83° (40-50 MPH) Req
0.85 3.1 1.0 3.2 0.9 3.1 0.7 23 - 55
0.90 3.2 1.2 3.3 1.1 3.3 0.9 23 - 59
0.95 3.5 1.2 3.5 1.1 3.6 1.0 22 - 62
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 2.6 0.4 NoRot N/A NoRot N/A 22 - 33
10 68° or 83° (40-50 MPH) Req
0.85 2.8 0.6 2.7 0.4 NoRot N/A 22 - 37
0.90 3.0 0.8 3.0 0.6 NoRot N/A 21 - 41
0.95 3.2 1.0 3.2 0.8 3.1 0.6 21 - 44
Table A.8 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 60
Knots (Slick ADE, 0.70-0.95M)
166
Boeing Report 15J0089
May 1, 2015
0.80 68° or 83° (40-60 MPH) Req 4.3 3.0 4.5 2.4 44 - 86
30
0.85 69° or 84° (60-70 MPH) Req 4.5 3.0 4.7 2.4 43 - 86
0.90 4.8 3.1 4.8 2.4 42 - 89
0.95 5.1 3.2 5.1 2.7 41 - 91
0.70 3.3 1.6 3.4 1.3 3.4 0.8 39 - 65
0.75 3.4 1.7 3.6 1.5 3.6 1.0 39 - 67
0.80 68° or 83° (40-60 MPH) Req 3.8 1.9 3.8 1.7 3.7 1.3 38 - 72
25
0.85 69° or 84° (60-70 MPH) Req 3.8 2.2 4.0 2.0 4.1 1.4 38 - 76
0.90 4.1 2.4 4.2 2.0 4.3 1.4 36 - 79
0.95 4.4 2.4 4.6 2.2 4.6 1.7 36 - 81
0.70 2.5 0.4 2.8 0.1 NoRot N/A 33 - 48
0.75 2.7 0.6 2.7 0.5 2.9 0.2 33 - 50
0.80 68° or 83° (40-60 MPH) Req 2.8 0.7 3.0 0.8 3.1 0.6 32 - 54
20
0.85 69° or 84° (60-70 MPH) Req 3.0 1.0 3.2 0.9 3.3 0.7 31 - 57
0.90 3.1 1.2 3.4 1.2 3.5 0.7 31 - 59
0.95 3.4 1.2 3.8 1.1 4.0 1.0 30 - 61
0.70 2.6 0.5 2.6 0.4 NoRot N/A 28 - 47
0.75 2.8 0.7 2.9 0.6 2.9 0.3 27 - 51
0.80 2.9 0.9 3.1 0.7 3.1 0.5 27 - 55
15 68° or 83° (40-50 MPH) Req
0.85 3.2 1.0 3.3 1.0 3.1 0.8 26 - 60
0.90 3.4 1.2 3.4 1.2 3.4 0.9 26 - 64
0.95 3.5 1.2 3.7 1.1 3.8 0.9 25 - 65
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 2.4 0.2 NoRot N/A NoRot N/A 24 - 33
0.80 2.7 0.5 2.7 0.3 NoRot N/A 23 - 40
12.5 68° or 83° (40-50 MPH) Req
0.85 2.9 0.7 3.0 0.5 2.7 0.2 23 - 45
0.90 3.0 0.9 3.1 0.8 3.1 0.5 22 - 47
0.95 3.2 0.9 3.4 0.8 3.4 0.6 22 - 48
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 NoRot N/A NoRot N/A NoRot N/A N/A
10 68° or 83° (40-50 MPH) Req
0.85 NoRot N/A NoRot N/A NoRot N/A N/A
0.90 2.8 0.4 NoRot N/A NoRot N/A 22 - 33
0.95 3.0 0.6 2.9 0.3 NoRot N/A 22 - 36
Table A.9 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 80
Knots (Slick ADE, 0.70-0.95M)
167
Boeing Report 15J0089
May 1, 2015
0.80 68° or 83° (40-60 MPH) Req 4.0 2.5 4.2 1.9 43 - 82
30
0.85 69° or 84° (60-70 MPH) Req 4.2 2.5 4.4 2.0 43 - 84
0.90 4.4 2.6 4.6 2.1 42 - 85
0.95 4.9 2.8 4.9 2.3 42 - 89
0.70 2.8 1.1 3.2 0.9 3.2 0.3 39 - 61
0.75 3.1 1.3 3.4 1.0 3.3 0.5 39 - 64
0.80 68° or 83° (40-60 MPH) Req 3.3 1.4 3.5 1.4 3.5 0.6 38 - 66
25
0.85 69° or 84° (60-70 MPH) Req 3.4 1.6 3.8 1.4 3.6 0.7 38 - 70
0.90 3.7 1.8 4.0 1.4 4.0 0.8 36 - 74
0.95 4.1 1.9 4.3 1.7 4.4 1.2 36 - 78
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 68° or 83° (40-60 MPH) Req 2.6 0.3 NoRot N/A 2.9 0.1 32 - 41
20
0.85 69° or 84° (60-70 MPH) Req 2.7 0.6 2.7 0.4 3.0 0.1 32 - 44
0.90 2.8 0.8 3.0 0.5 3.4 0.1 31 - 47
0.95 3.2 0.9 3.3 0.6 3.5 0.5 30 - 50
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 2.5 0.2 2.6 0.1 NoRot N/A 27 - 38
0.80 2.8 0.5 2.8 0.3 NoRot N/A 26 - 50
15 68° or 83° (40-50 MPH) Req
0.85 2.8 0.6 3.0 0.6 2.9 0.3 26 - 51
0.90 3.0 0.8 3.0 0.8 3.1 0.4 26 - 50
0.95 3.3 0.9 3.5 0.8 3.4 0.5 25 - 59
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 NoRot N/A NoRot N/A NoRot N/A N/A
12.5 68° or 83° (40-50 MPH) Req
0.85 2.6 0.2 NoRot N/A NoRot N/A 23 - 32
0.90 2.8 0.6 2.9 0.4 NoRot N/A 22 - 39
0.95 3.1 0.7 3.2 0.5 NoRot N/A 22 - 43
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 NoRot N/A NoRot N/A NoRot N/A N/A
10 68° or 83° (40-50 MPH) Req
0.85 NoRot N/A NoRot N/A NoRot N/A N/A
0.90 NoRot N/A NoRot N/A NoRot N/A N/A
0.95 NoRot N/A NoRot N/A NoRot N/A N/A
Table A.10 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 100
Knots (Slick ADE, 0.70-0.95M)
168
Boeing Report 15J0089
May 1, 2015
Each table is valid for the maximum wind listed at the top of the table and independent of wind direction.
All ROTs shown in this section do not require a velocity bias handed to the weapon, so impact angles of
70-90º can be commanded (provided impact azimuth is invalid for 83º or 84º to inhibit sending a velocity
bias to the weapon). The ROTs tables A.11 – A.15 are valid for 0-10 MPH, Omni-directional targets and
for maximum wind speeds of 20, 40, 60, 80 and 100 knots respectively.
169
Boeing Report 15J0089
May 1, 2015
Table A.11 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 20
Knots (Slick ADE, 0.70-0.95M)
170
Boeing Report 15J0089
May 1, 2015
Table A.12 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 40
Knots (Slick ADE, 0.70-0.95M)
171
Boeing Report 15J0089
May 1, 2015
Table A.13 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 60
Knots (Slick ADE, 0.70-0.95M)
172
Boeing Report 15J0089
May 1, 2015
Table A.14 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 80
Knots (Slick ADE, 0.70-0.95M)
173
Boeing Report 15J0089
May 1, 2015
Table A.15 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 100
Knots (Slick ADE, 0.70-0.95M)
174
Boeing Report 15J0089
May 1, 2015
A.2.3 Low HAT & Dive (0-40 MPH) Ground Range ROT Tables
During Block 9 development, a specific set of tables was requested to address LJDAM employment at
altitudes below 10 Kft HAT and at negative flight path angles. The tables in this section present ROTs for
0 – 40 MPH, omni-directional targets for release altitudes of 6 – 12.5 Kft HAT and dive angles from 0 to
negative 45 degrees. Each table is valid for the maximum wind listed at the top and is independent of wind
direction.
All ROTs shown in this section assume employment with a standard JDAM interface, meaning that
depending on the target speed range, a velocity bias must be handed to the weapon as indicated in the table.
For target speeds of 0 – 20 MPH, a zero velocity bias is specified and the impact angles command should
be set to 70º. For target speeds of 20 – 40 MPH, a 40 MPH velocity bias is specified and the impact angle
command should be set to 68º (with the azimuth validity set to valid and angle commanded to be the true
target direction). The ROTs tables A.16 – A.19 are valid for 0 – 40 MPH, omni-directional targets and for
maximum wind speeds of 20, 40, 60, and 80 knots respectively.
175
Boeing Report 15J0089
May 1, 2015
Table A.16 - LJDAM Ground Range Release Low HAT ROT for 0–40 mph for Winds Up To 20
Knots
176
Boeing Report 15J0089
May 1, 2015
Table A.17 - LJDAM Ground Range Release Low HAT ROT for 0–40 mph for Winds Up To 40
Knots
177
Boeing Report 15J0089
May 1, 2015
Table A.18 - LJDAM Ground Range Release Low HAT ROT for 0–40 mph for Winds Up To 60
Knots
178
Boeing Report 15J0089
May 1, 2015
Table A.19 - LJDAM Ground Range Release Low HAT ROT for 0–40 mph for Winds Up To 80
Knots
179
Boeing Report 15J0089
May 1, 2015
Release
Altitude (ft, Impact Bias Speed Target Speed True Target
MSL) Angle (deg) (mph) (mph) Direction (deg) Mach Footprint Chart
0.75
15,000 70 0.85 Figure A.10
0.95
N/A N/A 0.75
N/A
70 Stationary Stationary 0.85 Figure A.11
Stationary Target
Target Target 0.95
25,000
0.75
90 0.85 Figure A.12
0.95
N/A 0 deg Relative to 0.75
70 No Velocity 15 Weapon Release 0.85 Figure A.13
Bias Heading 0.95
15,000
45 deg Relative to 0.75
68 40 35 Weapon Release 0.85 Figure A.14
Heading 0.95
N/A 90 deg Relative to 0.75
90 No Velocity 15 Weapon Release 0.85 Figure A.15
Bias Heading 0.95
25,000
180 deg Relative to 0.75
83 40 35 Weapon Release 0.85 Figure A.16
Heading 0.95
N/A 45 deg Relative to 0.75
70 No Velocity 15 Weapon Release 0.85 Figure A.17
Bias Heading 0.95
35,000
90 deg Relative to 0.75
83 40 35 Weapon Release 0.85 Figure A.18
Heading 0.95
0 deg Relative to 0.75
10,000 69 60 50 Weapon Release 0.85 Figure A.19
Heading 0.95
0 deg Relative to 0.75
15,000 69 60 60 Weapon Release 0.85 Figure A.20
Heading 0.95
0 deg Relative to 0.75
25,000 69 60 60 Weapon Release 0.85 Figure A.21
Heading 0.95
-45 deg Relative to 0.75
84 60 70 Weapon Release 0.85 Figure A.22
Heading 0.95
35,000
-45 deg Relative to 0.75
69 60 60 Weapon Release 0.85 Figure A.23
Heading 0.95
Table A.20 – List of LJDAM Example Footprints (Slick ADE, Mach 0.70-0.95)
180
Boeing Report 15J0089
May 1, 2015
Figure A.10 – GBU-54 Stationary Target, Altitude = 15 kft, Impact Angle = 70 deg
Figure A.11 – GBU-54 Stationary Target, Altitude = 25 kft, Impact Angle = 70 deg
181
Boeing Report 15J0089
May 1, 2015
Figure A.12 – GBU-54 Stationary Target, Altitude = 25 kft, Impact Angle = 90 deg
Figure A.13 – GBU-54 Moving Target, No Velocity Bias, Altitude = 15 kft, (70 deg Impact Angle
Command), Target Speed = 15 mph
182
Boeing Report 15J0089
May 1, 2015
Figure A.14 – GBU-54 Moving Target, Velocity Bias, Altitude = 15 kft, Bias Speed = 40 mph (68 deg
Impact Angle Command), Target Speed = 35 mph
Figure A.15 – GBU-54 Moving Target, No Velocity Bias, Altitude = 25 kft, (90 deg Impact Angle
Command), Target Speed = 15 mph
183
Boeing Report 15J0089
May 1, 2015
Figure A.16 – GBU-54 Moving Target, Velocity Bias, Altitude = 25 kft, Bias Speed = 40 mph (83 deg
Impact Angle Command), Target Speed = 35 mph
Figure A.17 – GBU-54 Moving Target, No Velocity Bias, Altitude = 35 kft, (70 deg Impact Angle
Command), Target Speed = 15 mph
184
Boeing Report 15J0089
May 1, 2015
Figure A.18 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 40 mph (83 deg
Impact Angle Command), Target Speed = 35 mph
Figure A.19 – GBU-54 Moving Target, Velocity Bias, Altitude = 10 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 50 mph
185
Boeing Report 15J0089
May 1, 2015
Figure A.20 – GBU-54 Moving Target, Velocity Bias, Altitude = 15 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
Figure A.21 – GBU-54 Moving Target, Velocity Bias, Altitude = 25 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
186
Boeing Report 15J0089
May 1, 2015
Figure A.22 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 60 mph (84 deg
Impact Angle Command), Target Speed = 70 mph
Figure A.23 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
187
Boeing Report 15J0089
May 1, 2015
The energy capability curves provide a quick reference to help select release conditions that will ensure
there is a ROT available to pursue a specific target. The curves show the minimum energy (as a
combination of Mach and height above target) required to successfully engage a specific target speed and
target altitude. There are multiple curves on each plot and each represents a maximum wind limit in knots.
The legend describes the target altitude and maximum allowable wind magnitude. The curves are valid for
winds from any direction. In each plot, a valid ROT should exist for any Mach and altitude that is above
and to the right of the applicable curve as shown in Figure B.1. Mach and altitude combinations that are
below and to the left of the curve will not result in a valid ROT due to a combination of things: the
constraints of the ROT table (i.e., Omni-directional capability), and limited energy at release to satisfy all
requirements in the tables (i.e. meeting accuracy requirements in all specified wind conditions, target
directions, headings, etc). Knowing the maximum winds and target altitude for a specific mission should
help narrow down the minimum release speeds and altitudes required to engage either slow (0-40MPH) or
fast (40-70 MPH) moving targets.
The first three energy capability plots, Figures B.1-B3 show where ROTs exist at all release altitudes for
targets moving 0-40MPH in any direction (Omni-directional). Figures B.1, B.2 and B.3 show the results for
0, 5 and 10 Kft MSL target altitudes, respectively. Figures B.4 through B.6 show where ROTs exist at
release altitudes of 20Kft HAT and above against targets moving 40 to 70 MPH. Note fast mover ROTs
are restricted to a tail-chase constraint of +/- 45 degrees. That is, the aircraft heading must be within +/- 45
degrees of the target heading. Figures B.4, B.5 and B.6 show the results for 0, 5 and 10 Kft MSL target
altitudes, respectively. Figures B.7 through B.9 show where ROTs exist at release altitudes of 15Kft HAT
and below for targets moving 40 to 50 MPH. Figures B.7, B.8 and B.9 show the results for 0, 5 and 10 Kft
MSL target altitudes, respectively.
Figure B.1 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
0 Kft MSL Target
188
Boeing Report 15J0089
May 1, 2015
Figure B.2 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
5 Kft MSL Target Altitude
Figure B.3 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
10 Kft MSL Target Altitude
189
Boeing Report 15J0089
May 1, 2015
Figure B.4 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º
0 Kft MSL Target Altitude
Figure B.5 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º
5 Kft MSL Target Altitude
190
Boeing Report 15J0089
May 1, 2015
Figure B.6 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º
10 Kft MSL Target Altitude
Figure B.7 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
0 Kft MSL Target Altitude
191
Boeing Report 15J0089
May 1, 2015
Figure B.8 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
5 Kft MSL Target Altitude
Figure B.9 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
10 Kft MSL Target Altitude
192
Boeing Report 15J0089
May 1, 2015
ROT tables were tailored to address operator feedback on data organization. The general goal was to reduce
the amount of real-time decision making required during run-in to successfully employ the weapon.
Therefore all ROT tables are broken out for a maximum wind and are independent of wind direction. Once
a maximum wind for the day has been established, an appropriate table can be selected prior to the mission
and winds will not need real-time consideration. Tables are available that address slow moving (0-40 MPH)
and fast moving (40-70 MPH) targets. Block 8 (and later) software improvements have made it possible to
compute Omni-directional ROTs for slow moving targets (0-40MPH). Thus for slow movers, target
heading need not be a real-time consideration. ROTs for fast moving targets (40 -70 MPH) are still
restricted to a ±45º tail chase condition.
ROT results shown below are then valid for the maximum wind and target speeds listed at the top of each
table. They are independent of wind direction. The appropriate table for the mission is selected based on the
expected winds that day and expected target speeds to engage. Each table provides release slant range
distances for release altitudes of 10, 12.5, 15, 20, 25, 30 and 35 Kft HAT and for Mach points of 0.70, 0.75,
0.80, 0.85, 0.90 and 0.95. For each altitude and Mach combination, a release slant range distance is listed
for target altitudes of 0, 5 and 10 Kft MSL. No ROTs were provided for release altitudes above 35 Kft
MSL. Release altitudes at 40 Kft and above were not identified as high priority and data generation was
concentrated on lower altitude employment.
Under the target altitude columns, there is a release slant range distance to the target with a tolerance
denoted by the symbol “±”. So for example a release slant range distance of 3 nmi ± 1 nmi would represent
a 2 nmi long ROT box that is valid from 2 to 4 nmi slant range to the target. For a ROT to be considered
valid it should have a minimum of ±0.3 nmi of range depth. Cases where the ROT depth is less than 0.3
nmi in range are provided in the table but shown in red to help in interpolation between ROTs. Cases where
no ROT exists for that condition show up as “NoROT” in the table. The cross range tolerance on the ROT
box is a minimum of ± 0.3 nmi wide. Valid ROTs assume a weapon accuracy of 5m CEP for 0-40MPH
targets and 6m CEP for 40-70 MPH targets. They also assume that the achieved weapon impact angle is 30-
90º. All slant range release distances are only valid for the impact angle and impact azimuth commands
listed in the third and fourth columns. Note that the ROT boxes (i.e. the ROT +/- the tolerance) for each
case represents the un-conservative, maximized window for which the weapon can be employed. Similar
to JDAM baseline LARs, for the greatest probability of success it is advised to release as close to the ROT
center as possible.
The following two sections, B.2.1-B.2.2, show the generalized ROT tables and an additional set of tables
that are focused on special employment circumstances. Section B.2.1 shows the generalized ROT tables for
slow (0-40 MPH) and fast (40-70 MPH) moving targets. Section B.2.2 shows ROT tables for employment
against very slow movers (0-10 MPH) and is intended to supplement the general ROT tables in order to
open up capability for this specific condition. Section B.2.3 shows ROT tables for LJDAM employment at
altitudes below 10 Kft HAT and at negative flight path angles.
B.2.1 Slow (0-40MPH) and Fast (40-70MPH) Mover Slant Range ROT Tables
For the slow mover tables (0-40MPH), the impact angle command has two settings depending on the
estimated target speed. If the target is moving very slow, approximately 0-20 MPH, the ROT can be used
without passing a velocity bias to the weapon and impact angle commands of 70-90º can be used. Impact
azimuth command is not required and if not specifically needed, should be set as invalid. If a target is
moving in the range of 20-40 MPH, the ROT can be used by commanding an impact angle of 68º or 83º,
which passes a 40 MPH velocity bias to the weapon. In this case the impact azimuth command should be
valid and used to specify the target heading at release (See Table 8.9 – Block 9 Manual Mode Velocity Bias
Logic Summary).
193
Boeing Report 15J0089
May 1, 2015
There is no significant change in weapon performance at a target speed breakpoints found in the table and
some degree of overlap is acceptable. For example at 20 MPH, some overlap exists where either impact
angle command can be used, that is, one that specifies no velocity bias (70-90º) or one that specifies a 40
MPH velocity bias (68º or 83º). When choosing the appropriate impact angle command and velocity bias,
the weapon performance is optimized by passing the weapon the closest approximation possible to the
target’s true speed. Each slant range release distance shown in the table is valid for either case (i.e., either
using 70-90º impact angle command with an invalid azimuth command for 0-20 MPH targets or a 68º/83º
impact angle command with a valid azimuth command defining the target heading for 20-40 MPH targets).
Similarly for the fast mover tables (40-70 MPH) at high HAT release conditions of 20-35Kft HAT, there
are two settings for impact angle command. For targets moving 40-60 MPH, the ROTs can be used by
commanding an impact angle of 68º or 83º (40 MPH bias) and for targets moving 60-70 MPH, the ROTs
can be used by commanding an impact angle of 69º or 84º (60 MPH bias). In either case, the impact
azimuth command should again be valid and used to specify the target heading at release.
For low HAT release conditions of 10-15Kft, the ROTs in the fast mover table are only provided for target
speeds up to 50 MPH. At low release altitudes performance degrades against 50-70 MPH targets. The ROT
capability is much greater by only engaging targets up to 50 MPH at this altitude. For these low HAT
conditions engaging target speeds of 40-50 MPH, the ROTs can be used by commanding an impact angle
of 68º or 83º (40 MPH bias) and specifying target heading via the azimuth command.
Note that the slant range distances are distances to the target at weapon separation, not weapon pickle. An
additional downrange increment should be added based on the specific aircraft pickle duration and aircraft
inertial speed at release.
Tables B.1 - B.5 provide the Rules of Thumb for Omni-directional targets of speeds between 0-40 MPH for
wind limits of 20, 40, 60, 80, and 100 knots respectively. Tables B.6 - B.10 provide the Rules of Thumb for
targets of speeds between 40-70 MPH, subject to a ±45º tail chase condition, for wind limits of 20, 40, 60,
80, and 100 knots respectively.
To reduce the amount of real-time lookup aircrews must accomplish, the intent here is that they select the
appropriate table from below prior to the mission based on winds that day and anticipated target speeds.
For example if winds are 30-40 knots and target speeds are expected to be 0-40 MPH, Table B.2 would be
selected as that data is for slow movers and valid up to maximum wind speeds of 40 knots. (As noted, all
the ROT tables below are independent of wind direction).
Once the table is selected the aircrew can mission plan their release altitude and airspeed based upon the
capability of the aircraft and weapon at the expected target altitude. For slow movers, the operator should
only have to check the release slant range and set the impact angle commands to employ the weapon. To
engage fast moving targets the aircraft would also need to be in a tail chase condition.
In the unique case where the target is fixed or moving approximately 20 MPH or slower, it is possible to set
the impact angle command anywhere between 70-90º prior to run on the target (bearing in mind that impact
azimuth command should be invalid for impact angle commands of 83º and 84º to inhibit sending a
velocity bias to the weapon). Then there is only one real-time parameter to consider - the correct release
slant range distance to the target.
194
Boeing Report 15J0089
May 1, 2015
0.80 70°-90° (0-20 MPH) Not Req 8.2 3.1 8.2 3.0 43 - 101
30
0.85 68° or 83° (20-40MPH) Req 8.3 3.2 8.5 3.1 42 - 103
0.90 8.5 3.3 8.6 3.2 42 - 106
0.95 8.7 3.4 8.8 3.3 41 - 107
0.70 6.7 2.2 6.6 2.0 6.3 1.4 39 - 84
0.75 6.9 2.4 6.9 2.2 6.5 1.6 39 - 87
0.80 70°-90° (0-20 MPH) Not Req 7.2 2.6 7.1 2.4 6.7 1.8 38 - 91
25
0.85 68° or 83° (20-40MPH) Req 7.3 2.9 7.2 2.7 7.8 1.2 38 - 94
0.90 7.6 3.1 7.4 2.7 8.1 1.1 36 - 97
0.95 7.7 3.1 7.8 2.9 8.6 1.3 36 - 98
0.70 5.5 1.7 5.5 1.5 5.3 1.1 33 - 72
0.75 5.7 1.9 5.7 1.7 5.5 1.3 33 - 75
0.80 70°-90° (0-20 MPH) Not Req 6.0 2.0 6.0 1.9 5.8 1.6 32 - 78
20
0.85 68° or 83° (20-40MPH) Req 6.2 2.2 6.1 2.1 5.9 1.8 31 - 81
0.90 6.3 2.4 6.4 2.4 6.2 1.9 31 - 84
0.95 6.6 2.5 6.7 2.5 6.6 2.3 30 - 87
0.70 4.3 1.0 4.3 0.9 4.3 0.7 28 - 59
0.75 4.4 1.1 4.5 1.0 4.5 0.9 27 - 63
0.80 70°-90° (0-20 MPH) Not Req 4.6 1.2 4.7 1.2 4.7 1.0 26 - 66
15
0.85 68° or 83° (20-40MPH) Req 4.6 1.2 4.9 1.3 4.9 1.1 26 - 69
0.90 4.7 1.3 5.0 1.3 5.0 1.2 26 - 71
0.95 4.9 1.4 5.1 1.4 5.2 1.3 25 - 74
0.70 3.8 0.8 3.8 0.7 3.8 0.5 25 - 52
0.75 4.0 0.9 4.0 0.8 4.0 0.6 24 - 55
0.80 70°-90° (0-20 MPH) Not Req 4.1 1.0 4.1 0.9 4.2 0.8 24 - 59
12.5
0.85 68° or 83° (20-40MPH) Req 4.1 1.0 4.3 1.0 4.4 0.9 23 - 62
0.90 4.2 1.1 4.5 1.1 4.5 1.0 23 - 65
0.95 4.4 1.1 4.6 1.2 4.7 1.1 22 - 67
0.70 3.3 0.5 3.4 0.4 NoRot N/A 22 - 41
0.75 3.4 0.6 3.5 0.5 3.4 0.2 22 - 45
0.80 70°-90° (0-20 MPH) Not Req 3.5 0.7 3.6 0.6 3.6 0.4 21 - 49
10
0.85 68° or 83° (20-40MPH) Req 3.8 0.8 3.9 0.7 3.8 0.6 21 - 53
0.90 3.8 0.9 4.0 0.8 4.0 0.7 21 - 56
0.95 4.1 1.0 4.2 0.9 4.2 0.8 20 - 60
Table B.1- LJDAM Slant Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 20 Knots
(Slick ADE, Mach 0.70-0.95)
195
Boeing Report 15J0089
May 1, 2015
0.80 70°-90° (0-20 MPH) Not Req 8.0 2.9 8.1 2.7 43 - 100
30
0.85 68° or 83° (20-40MPH) Req 8.2 3.0 8.2 2.9 42 - 102
0.90 8.3 3.1 8.4 2.9 42 - 104
0.95 8.5 3.2 8.6 3.1 41 - 106
0.70 6.5 2.0 6.4 1.7 6.5 0.6 39 - 83
0.75 6.6 2.1 6.7 2.0 6.8 0.8 38 - 85
0.80 70°-90° (0-20 MPH) Not Req 7.0 2.4 6.8 2.2 7.2 0.8 38 - 89
25
0.85 68° or 83° (20-40MPH) Req 7.1 2.6 7.0 2.3 7.6 0.6 38 - 91
0.90 7.3 2.8 7.3 2.4 5.7 0.5 36 - 94
0.95 7.6 2.9 7.6 2.6 6.0 0.7 35 - 97
0.70 5.3 1.4 5.3 1.2 5.2 0.8 33 - 70
0.75 5.6 1.6 5.5 1.3 5.4 1.0 32 - 73
0.80 70°-90° (0-20 MPH) Not Req 5.8 1.7 5.7 1.5 5.7 1.3 32 - 76
20
0.85 68° or 83° (20-40MPH) Req 5.9 1.9 5.8 1.8 5.7 1.5 31 - 79
0.90 6.1 2.1 6.2 2.1 5.9 1.5 31 - 82
0.95 6.3 2.2 6.5 2.2 6.4 1.9 30 - 84
0.70 4.2 0.8 4.2 0.7 4.3 0.5 28 - 56
0.75 4.3 0.8 4.4 0.9 4.4 0.7 27 - 60
0.80 70°-90° (0-20 MPH) Not Req 4.3 0.9 4.6 1.0 4.6 0.8 26 - 63
15
0.85 68° or 83° (20-40MPH) Req 4.5 0.9 4.7 1.0 4.8 0.9 26 - 66
0.90 4.6 1.1 4.8 1.1 4.9 1.0 25 - 70
0.95 4.8 1.2 4.9 1.1 5.1 1.1 25 - 71
0.70 3.7 0.6 3.7 0.5 NoRot N/A 25 - 47
0.75 3.8 0.6 3.9 0.5 3.9 0.4 24 - 52
0.80 70°-90° (0-20 MPH) Not Req 3.9 0.7 4.0 0.7 4.0 0.6 24 - 55
12.5
0.85 68° or 83° (20-40MPH) Req 4.0 0.7 4.1 0.7 4.3 0.7 23 - 58
0.90 4.1 0.9 4.3 0.9 4.5 0.8 23 - 62
0.95 4.3 1.0 4.4 0.9 4.5 0.9 22 - 64
0.70 3.1 0.2 NoRot N/A NoRot N/A 23 - 31
0.75 3.3 0.4 3.2 0.2 NoRot N/A 22 - 36
0.80 70°-90° (0-20 MPH) Not Req 3.5 0.6 3.5 0.4 3.4 0.1 21 - 45
10
0.85 68° or 83° (20-40MPH) Req 3.6 0.6 3.7 0.5 3.7 0.4 20 - 46
0.90 3.8 0.8 3.9 0.7 3.9 0.5 21 - 53
0.95 4.0 0.8 4.1 0.8 4.2 0.6 20 - 58
Table B.2 – LJDAM Slant Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 40 Knots
(Slick ADE, Mach 0.70-0.95)
196
Boeing Report 15J0089
May 1, 2015
0.80 70°-90° (0-20 MPH) Not Req 7.7 2.6 7.8 2.4 43 - 97
30
0.85 68° or 83° (20-40MPH) Req 7.8 2.7 7.8 2.5 42 - 99
0.90 8.1 2.8 8.2 2.6 42 - 102
0.95 8.1 2.7 8.5 2.8 41 - 100
0.70 6.4 1.7 6.2 1.4 6.5 0.2 38 - 80
0.75 6.5 1.8 6.4 1.6 6.7 0.3 38 - 83
0.80 70°-90° (0-20 MPH) Not Req 6.7 2.0 6.6 1.9 5.4 0.4 37 - 86
25
0.85 68° or 83° (20-40MPH) Req 6.8 2.2 6.8 2.0 5.6 0.4 37 - 89
0.90 7.1 2.5 7.0 2.1 5.7 0.4 36 - 92
0.95 7.3 2.5 7.2 2.1 5.9 0.5 35 - 95
0.70 5.1 1.0 5.0 0.8 5.0 0.4 33 - 65
0.75 5.3 1.2 5.2 1.0 5.3 0.7 32 - 69
0.80 70°-90° (0-20 MPH) Not Req 5.4 1.3 5.3 1.1 5.4 0.9 32 - 72
20
0.85 68° or 83° (20-40MPH) Req 5.5 1.5 5.5 1.3 5.5 1.0 31 - 75
0.90 5.6 1.6 5.7 1.6 5.5 0.9 31 - 77
0.95 5.9 1.7 6.0 1.7 6.0 1.3 30 - 81
0.70 4.0 0.5 4.1 0.4 NoRot N/A 28 - 52
0.75 4.1 0.6 4.3 0.6 4.1 0.2 27 - 56
0.80 70°-90° (0-20 MPH) Not Req 4.2 0.6 4.4 0.7 4.3 0.4 26 - 58
15
0.85 68° or 83° (20-40MPH) Req 4.3 0.7 4.4 0.7 4.6 0.5 26 - 62
0.90 4.4 0.8 4.6 0.8 4.7 0.7 25 - 64
0.95 4.6 1.0 4.7 0.9 4.8 0.8 25 - 66
0.70 NoRot N/A NoRot N/A NoRot N/A 25 - 41
0.75 NoRot N/A NoRot N/A NoRot N/A 24 - 46
0.80 70°-90° (0-20 MPH) Not Req 3.6 0.4 3.8 0.3 3.8 0.1 24 - 50
12.5
0.85 68° or 83° (20-40MPH) Req 3.9 0.5 4.0 0.5 4.0 0.3 23 - 54
0.90 4.0 0.6 4.1 0.6 4.2 0.4 23 - 59
0.95 4.2 0.8 4.3 0.7 4.4 0.6 22 - 62
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 70°-90° (0-20 MPH) Not Req 3.3 0.2 NoRot N/A NoRot N/A 22 - 34
10
0.85 68° or 83° (20-40MPH) Req 3.6 0.4 3.6 0.2 NoRot N/A 21 - 39
0.90 3.8 0.6 3.8 0.4 3.7 0.1 21 - 43
0.95 3.9 0.7 4.1 0.5 4.0 0.4 20 - 51
Table B.3 - LJDAM Slant Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 60 Knots
(Slick ADE, Mach 0.70-0.95)
197
Boeing Report 15J0089
May 1, 2015
0.80 70°-90° (0-20 MPH) Not Req 7.6 2.3 7.5 2.1 43 - 95
30
0.85 68° or 83° (20-40MPH) Req 7.7 2.4 7.6 2.2 42 - 98
0.90 7.8 2.5 7.9 2.3 41 - 100
0.95 7.8 2.4 8.2 2.5 41 - 97
0.70 6.0 1.4 5.9 1.0 NoRot N/A 39 - 77
0.75 6.2 1.4 6.2 1.2 NoRot N/A 38 - 80
0.80 70°-90° (0-20 MPH) Not Req 6.3 1.6 6.4 1.6 5.7 0.2 37 - 83
25
0.85 68° or 83° (20-40MPH) Req 6.5 1.8 6.6 1.7 5.6 0.3 37 - 86
0.90 6.8 2.1 6.6 1.6 5.7 0.3 36 - 90
0.95 6.8 2.0 6.9 1.8 5.9 0.4 36 - 89
0.70 4.8 0.6 4.8 0.5 5.1 0.1 33 - 59
0.75 4.9 0.7 5.0 0.5 5.3 0.2 32 - 61
0.80 70°-90° (0-20 MPH) Not Req 4.9 0.7 4.6 0.3 5.5 0.2 32 - 62
20
0.85 68° or 83° (20-40MPH) Req 4.9 0.8 5.1 0.9 4.9 0.4 31 - 64
0.90 5.1 1.0 5.4 1.2 5.1 0.5 31 - 68
0.95 5.3 1.1 5.5 1.1 5.5 0.8 30 - 71
0.70 NoRot N/A NoRot N/A NoRot N/A 28 - 46
0.75 3.9 0.2 NoRot N/A NoRot N/A 27 - 49
0.80 70°-90° (0-20 MPH) Not Req 4.0 0.4 4.0 0.2 NoRot N/A 26 - 53
15
0.85 68° or 83° (20-40MPH) Req 4.1 0.5 4.3 0.3 4.3 0.2 26 - 56
0.90 4.3 0.6 4.5 0.5 4.5 0.3 25 - 60
0.95 4.5 0.7 4.5 0.6 4.6 0.5 25 - 63
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A 24 - 37
0.80 70°-90° (0-20 MPH) Not Req NoRot N/A NoRot N/A NoRot N/A 24 - 40
12.5
0.85 68° or 83° (20-40MPH) Req NoRot N/A NoRot N/A NoRot N/A 23 - 46
0.90 3.9 0.5 4.0 0.4 4.0 0.1 23 - 54
0.95 4.1 0.6 4.2 0.5 4.3 0.4 22 - 55
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 70°-90° (0-20 MPH) Not Req NoRot N/A NoRot N/A NoRot N/A N/A
10
0.85 68° or 83° (20-40MPH) Req NoRot N/A NoRot N/A NoRot N/A 22 - 32
0.90 NoRot N/A NoRot N/A NoRot N/A 21 - 37
0.95 NoRot N/A NoRot N/A NoRot N/A 20 - 44
Table B.4 - LJDAM Slant Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 80 Knots
(Slick ADE, Mach 0.70-0.95)
198
Boeing Report 15J0089
May 1, 2015
0.80 70°-90° (0-20 MPH) Not Req 7.2 1.9 7.3 1.7 42 - 92
30
0.85 68° or 83° (20-40MPH) Req 7.4 2.0 7.4 1.8 42 - 94
0.90 7.5 2.0 7.7 1.9 41 - 93
0.95 7.6 2.0 8.0 2.0 41 - 94
0.70 5.4 0.5 5.7 0.6 NoRot N/A 39 - 64
0.75 5.5 0.7 6.0 0.9 NoRot N/A 38 - 70
0.80 70°-90° (0-20 MPH) Not Req 5.9 1.0 6.0 1.1 5.5 0.1 37 - 75
25
0.85 68° or 83° (20-40MPH) Req 6.0 1.3 6.3 1.3 5.7 0.1 37 - 78
0.90 6.4 1.6 6.4 1.3 5.7 0.2 36 - 84
0.95 6.4 1.4 6.7 1.4 5.9 0.3 35 - 83
0.70 4.6 0.4 4.7 0.1 NoRot N/A 33 - 56
0.75 4.7 0.3 4.8 0.3 NoRot N/A 32 - 57
0.80 70°-90° (0-20 MPH) Not Req 4.7 0.2 5.1 0.2 NoRot N/A 32 - 58
20
0.85 68° or 83° (20-40MPH) Req 4.6 0.2 5.3 0.3 4.8 0.1 31 - 61
0.90 4.5 0.3 4.7 0.2 5.0 0.2 31 - 52
0.95 4.9 0.5 5.1 0.6 5.2 0.4 30 - 61
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 70°-90° (0-20 MPH) Not Req NoRot N/A NoRot N/A NoRot N/A 26 - 44
15
0.85 68° or 83° (20-40MPH) Req 4.0 0.2 NoRot N/A NoRot N/A 26 - 46
0.90 4.3 0.4 4.3 0.3 NoRot N/A 25 - 49
0.95 4.4 0.6 4.5 0.4 4.5 0.2 25 - 61
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 70°-90° (0-20 MPH) Not Req NoRot N/A NoRot N/A NoRot N/A 24 - 36
12.5
0.85 68° or 83° (20-40MPH) Req NoRot N/A NoRot N/A NoRot N/A 23 - 40
0.90 NoRot N/A NoRot N/A NoRot N/A 23 - 42
0.95 NoRot N/A NoRot N/A NoRot N/A 22 - 47
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 70°-90° (0-20 MPH) Not Req NoRot N/A NoRot N/A NoRot N/A N/A
10
0.85 68° or 83° (20-40MPH) Req NoRot N/A NoRot N/A NoRot N/A N/A
0.90 NoRot N/A NoRot N/A NoRot N/A N/A
0.95 NoRot N/A NoRot N/A NoRot N/A 21 - 36
Table B.5 - LJDAM Slant Range Release Rule of Thumb for 0 – 40 mph for Winds Up To 100 Knots
(Slick ADE, Mach 0.70-0.95)
199
Boeing Report 15J0089
May 1, 2015
30
0.85 69° or 84° (60-70 MPH) Req 7.7 2.7 7.6 2.4 43 - 92
0.90 7.8 2.8 7.8 2.5 42 - 93
0.95 8.2 3.1 8.2 2.8 41 - 98
0.70 6.1 1.8 6.0 1.6 5.9 1.3 39 - 74
0.75 6.2 1.9 6.3 1.8 6.1 1.5 39 - 77
0.80 68° or 83° (40-60 MPH) Req 6.4 2.1 6.4 1.9 6.3 1.7 38 - 80
25
0.85 69° or 84° (60-70 MPH) Req 6.7 2.4 6.5 2.2 6.4 1.8 38 - 84
0.90 6.8 2.6 6.8 2.3 6.7 1.9 37 - 86
0.95 7.0 2.6 7.1 2.5 7.0 2.2 36 - 88
0.70 4.9 1.3 4.9 1.2 4.8 0.9 33 - 62
0.75 5.1 1.4 5.1 1.3 5.0 1.1 33 - 65
0.80 68° or 83° (40-60 MPH) Req 5.3 1.6 5.3 1.5 5.2 1.3 32 - 68
20
0.85 69° or 84° (60-70 MPH) Req 5.4 1.8 5.5 1.7 5.3 1.5 32 - 71
0.90 5.6 1.9 5.7 2.0 5.5 1.5 31 - 74
0.95 5.9 2.1 5.9 2.0 5.9 1.8 30 - 78
0.70 4.1 1.2 4.1 1.0 4.1 0.9 28 - 56
0.75 4.3 1.3 4.3 1.2 4.3 1.0 27 - 61
0.80 4.5 1.5 4.5 1.4 4.5 1.2 27 - 65
15 68° or 83° (40-50 MPH) Req
0.85 4.7 1.6 4.7 1.6 4.6 1.4 26 - 68
0.90 4.9 1.8 4.9 1.8 4.8 1.6 26 - 71
0.95 5.1 2.0 5.1 1.8 5.2 1.7 25 - 74
0.70 3.6 0.9 3.6 0.8 3.5 0.6 25 - 49
0.75 3.8 1.0 3.8 0.9 3.7 0.8 24 - 53
0.80 3.9 1.2 4.0 1.1 3.9 0.9 24 - 57
12.5 68° or 83° (40-50 MPH) Req
0.85 4.1 1.4 4.1 1.3 4.1 1.1 23 - 61
0.90 4.3 1.5 4.4 1.5 4.3 1.4 23 - 63
0.95 4.6 1.6 4.6 1.5 4.6 1.5 22 - 68
0.70 3.1 0.6 3.0 0.4 NoRot N/A 23 - 39
0.75 3.3 0.8 3.2 0.6 3.1 0.2 22 - 43
0.80 3.4 0.9 3.5 0.8 3.3 0.5 21 - 46
10 68° or 83° (40-50 MPH) Req
0.85 3.6 1.0 3.6 1.0 3.6 0.7 21 - 50
0.90 3.8 1.2 3.8 1.1 3.8 1.0 21 - 56
0.95 4.0 1.3 4.0 1.2 4.0 1.1 21 - 60
Table B.6 – LJDAM Slant Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 20 Knots
(Slick ADE, Mach 0.70-0.95)
200
Boeing Report 15J0089
May 1, 2015
30
0.85 69° or 84° (60-70 MPH) Req 7.4 2.4 7.4 2.2 42 - 89
0.90 7.7 2.6 7.6 2.3 42 - 93
0.95 7.8 2.7 8.0 2.6 41 - 94
0.70 5.8 1.5 5.8 1.4 5.7 1.0 39 - 72
0.75 6.0 1.7 5.9 1.5 5.9 1.2 39 - 76
0.80 68° or 83° (40-60 MPH) Req 6.2 1.9 6.2 1.7 6.0 1.4 38 - 78
25
0.85 69° or 84° (60-70 MPH) Req 6.4 2.1 6.2 1.9 6.2 1.6 38 - 82
0.90 6.6 2.3 6.6 2.0 6.4 1.6 36 - 86
0.95 6.9 2.4 6.9 2.2 6.8 2.0 36 - 87
0.70 4.7 1.0 4.7 0.9 4.6 0.6 33 - 60
0.75 4.9 1.2 4.9 1.1 4.9 0.8 33 - 62
0.80 68° or 83° (40-60 MPH) Req 5.0 1.3 5.1 1.2 5.0 1.0 32 - 64
20
0.85 69° or 84° (60-70 MPH) Req 5.2 1.4 5.3 1.5 5.1 1.1 31 - 68
0.90 5.4 1.6 5.4 1.7 5.4 1.2 31 - 72
0.95 5.5 1.7 5.7 1.6 5.6 1.5 30 - 74
0.70 3.9 0.9 4.0 0.8 3.9 0.6 28 - 54
0.75 4.2 1.1 4.1 1.0 4.1 0.8 27 - 59
0.80 4.3 1.2 4.3 1.1 4.3 0.9 27 - 61
15 68° or 83° (40-50 MPH) Req
0.85 4.4 1.4 4.5 1.3 4.5 1.2 26 - 64
0.90 4.7 1.5 4.7 1.5 4.6 1.3 26 - 69
0.95 4.9 1.7 4.9 1.6 5.0 1.5 25 - 72
0.70 3.4 0.7 3.4 0.5 3.4 0.4 25 - 47
0.75 3.6 0.8 3.6 0.7 3.6 0.5 24 - 50
0.80 3.8 1.0 3.8 0.9 3.8 0.7 24 - 54
12.5 68° or 83° (40-50 MPH) Req
0.85 3.9 1.1 3.9 1.0 3.9 0.9 23 - 58
0.90 4.0 1.2 4.2 1.2 4.1 1.1 23 - 61
0.95 4.3 1.3 4.4 1.3 4.4 1.2 22 - 65
0.70 2.8 0.3 NoRot N/A NoRot N/A 22 - 32
0.75 3.0 0.5 3.0 0.3 NoRot N/A 22 - 35
0.80 3.2 0.7 3.2 0.5 NoRot N/A 21 - 39
10 68° or 83° (40-50 MPH) Req
0.85 3.4 0.8 3.4 0.7 3.3 0.4 21 - 42
0.90 3.6 0.9 3.6 0.8 3.6 0.7 21 - 52
0.95 3.8 1.1 3.9 1.0 3.8 0.9 21 - 54
Table B.7 – LJDAM Slant Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 40 Knots
(Slick ADE, Mach 0.70-0.95)
201
Boeing Report 15J0089
May 1, 2015
30
0.85 69° or 84° (60-70 MPH) Req 7.3 2.3 7.2 1.9 42 - 89
0.90 7.5 2.3 7.4 2.0 41 - 90
0.95 7.7 2.5 7.7 2.2 41 - 93
0.70 5.6 1.3 5.6 1.1 5.6 0.8 39 - 69
0.75 5.8 1.4 5.8 1.2 5.7 0.9 39 - 71
0.80 68° or 83° (40-60 MPH) Req 5.9 1.4 6.0 1.5 5.9 1.1 38 - 73
25
0.85 69° or 84° (60-70 MPH) Req 6.1 1.8 6.1 1.6 6.0 1.2 38 - 79
0.90 6.4 2.0 6.2 1.7 6.2 1.3 36 - 83
0.95 6.6 2.1 6.6 1.9 6.5 1.6 36 - 85
0.70 4.4 0.6 4.5 0.6 4.5 0.3 33 - 56
0.75 4.5 0.7 4.7 0.7 4.6 0.5 33 - 58
0.80 68° or 83° (40-60 MPH) Req 4.6 0.9 4.9 0.9 4.8 0.8 32 - 60
20
0.85 69° or 84° (60-70 MPH) Req 4.8 1.1 4.9 1.1 4.9 0.8 31 - 63
0.90 5.0 1.2 5.1 1.2 5.1 0.9 31 - 67
0.95 5.1 1.2 5.3 1.2 5.5 1.2 30 - 67
0.70 3.8 0.7 3.8 0.5 3.7 0.3 28 - 51
0.75 4.0 0.8 3.9 0.7 4.0 0.5 27 - 56
0.80 4.1 1.0 4.1 0.9 4.1 0.7 27 - 60
15 68° or 83° (40-50 MPH) Req
0.85 4.2 1.1 4.2 1.0 4.2 0.9 26 - 62
0.90 4.3 1.2 4.4 1.2 4.5 1.1 26 - 64
0.95 4.6 1.3 4.8 1.3 4.7 1.2 25 - 68
0.70 3.2 0.4 3.2 0.2 NoRot N/A 24 - 39
0.75 3.4 0.5 3.4 0.4 3.3 0.1 24 - 45
0.80 3.5 0.7 3.6 0.6 3.5 0.4 23 - 47
12.5 68° or 83° (40-50 MPH) Req
0.85 3.7 0.8 3.8 0.7 3.7 0.6 23 - 55
0.90 3.9 1.0 3.9 0.9 3.9 0.8 23 - 59
0.95 4.1 1.0 4.1 1.0 4.2 0.8 22 - 62
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 3.1 0.4 NoRot N/A NoRot N/A 22 - 33
10 68° or 83° (40-50 MPH) Req
0.85 3.2 0.5 3.1 0.3 NoRot N/A 22 - 37
0.90 3.5 0.7 3.5 0.5 NoRot N/A 21 - 41
0.95 3.6 0.9 3.6 0.7 3.5 0.5 21 - 44
Table B.8 - LJDAM Slant Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 60 Knots
(Slick ADE, Mach 0.70-0.95)
202
Boeing Report 15J0089
May 1, 2015
30
0.85 69° or 84° (60-70 MPH) Req 7.0 1.9 7.1 1.6 43 - 86
0.90 7.3 2.0 7.1 1.6 42 - 89
0.95 7.5 2.2 7.4 1.8 41 - 91
0.70 5.4 1.0 5.4 0.8 5.4 0.5 39 - 65
0.75 5.5 1.0 5.6 1.0 5.5 0.7 39 - 67
0.80 68° or 83° (40-60 MPH) Req 5.8 1.2 5.7 1.1 5.6 0.8 38 - 72
25
0.85 69° or 84° (60-70 MPH) Req 5.9 1.5 5.9 1.3 5.9 0.9 38 - 76
0.90 6.1 1.6 6.1 1.4 6.1 1.0 36 - 79
0.95 6.2 1.7 6.3 1.6 6.3 1.3 36 - 81
0.70 4.1 0.2 4.3 0.0 NoRot N/A 33 - 48
0.75 4.3 0.4 4.3 0.3 4.4 0.1 33 - 50
0.80 68° or 83° (40-60 MPH) Req 4.3 0.5 4.5 0.5 4.6 0.4 32 - 54
20
0.85 69° or 84° (60-70 MPH) Req 4.5 0.6 4.6 0.6 4.7 0.5 31 - 57
0.90 4.6 0.8 4.8 0.8 4.9 0.5 31 - 59
0.95 4.8 0.8 5.0 0.8 5.2 0.8 30 - 61
0.70 3.6 0.4 3.6 0.2 NoRot N/A 28 - 47
0.75 3.7 0.5 3.8 0.4 3.8 0.2 27 - 51
0.80 3.9 0.7 4.0 0.6 4.0 0.4 27 - 55
15 68° or 83° (40-50 MPH) Req
0.85 4.1 0.8 4.2 0.8 4.0 0.6 26 - 60
0.90 4.2 0.9 4.2 0.9 4.3 0.7 26 - 64
0.95 4.4 1.0 4.5 0.9 4.5 0.8 25 - 65
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 3.1 0.2 NoRot N/A NoRot N/A 24 - 33
0.80 3.4 0.4 3.4 0.2 NoRot N/A 23 - 40
12.5 68° or 83° (40-50 MPH) Req
0.85 3.6 0.5 3.6 0.4 3.4 0.2 23 - 45
0.90 3.7 0.7 3.8 0.7 3.7 0.4 22 - 47
0.95 3.8 0.8 4.0 0.7 4.0 0.5 22 - 48
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 NoRot N/A NoRot N/A NoRot N/A N/A
10 68° or 83° (40-50 MPH) Req
0.85 NoRot N/A NoRot N/A NoRot N/A N/A
0.90 3.2 0.4 NoRot N/A NoRot N/A 22 - 33
0.95 3.4 0.5 3.3 0.2 NoRot N/A 22 - 36
Table B.9 - LJDAM Slant Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 80 Knots
(Slick ADE, Mach 0.70-0.95)
203
Boeing Report 15J0089
May 1, 2015
30
0.85 69° or 84° (60-70 MPH) Req 6.8 1.6 6.8 1.3 43 - 84
0.90 6.9 1.6 6.9 1.4 42 - 85
0.95 7.2 1.9 7.2 1.6 42 - 89
0.70 5.1 0.6 5.3 0.6 5.2 0.2 39 - 61
0.75 5.2 0.7 5.4 0.6 5.3 0.3 39 - 64
0.80 68° or 83° (40-60 MPH) Req 5.4 0.8 5.5 0.9 5.4 0.4 38 - 66
25
0.85 69° or 84° (60-70 MPH) Req 5.5 1.0 5.7 0.9 5.5 0.4 38 - 70
0.90 5.7 1.2 5.9 1.0 5.8 0.6 36 - 74
0.95 6.0 1.3 6.1 1.2 6.1 0.9 36 - 78
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 68° or 83° (40-60 MPH) Req 4.2 0.2 NoRot N/A 4.4 0.0 32 - 41
20
0.85 69° or 84° (60-70 MPH) Req 4.3 0.4 4.3 0.2 4.4 0.1 32 - 44
0.90 4.4 0.5 4.5 0.4 4.7 0.0 31 - 47
0.95 4.6 0.6 4.7 0.4 4.8 0.3 30 - 50
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 3.5 0.2 3.6 0.1 NoRot N/A 27 - 38
0.80 3.7 0.3 3.7 0.2 NoRot N/A 26 - 50
15 68° or 83° (40-50 MPH) Req
0.85 3.8 0.5 3.9 0.4 3.8 0.2 26 - 51
0.90 3.9 0.6 4.0 0.6 4.0 0.3 26 - 50
0.95 4.1 0.7 4.3 0.6 4.2 0.4 25 - 59
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 NoRot N/A NoRot N/A NoRot N/A N/A
12.5 68° or 83° (40-50 MPH) Req
0.85 3.3 0.2 NoRot N/A NoRot N/A 23 - 32
0.90 3.5 0.5 3.6 0.3 NoRot N/A 22 - 39
0.95 3.7 0.6 3.8 0.4 NoRot N/A 22 - 43
0.70 NoRot N/A NoRot N/A NoRot N/A N/A
0.75 NoRot N/A NoRot N/A NoRot N/A N/A
0.80 NoRot N/A NoRot N/A NoRot N/A N/A
10 68° or 83° (40-50 MPH) Req
0.85 NoRot N/A NoRot N/A NoRot N/A N/A
0.90 NoRot N/A NoRot N/A NoRot N/A N/A
0.95 NoRot N/A NoRot N/A NoRot N/A N/A
Table B.10 - LJDAM Slant Range Release Rule of Thumb for 40 – 70 mph for Winds Up To 100
Knots (Slick ADE, Mach 0.70-0.95)
204
Boeing Report 15J0089
May 1, 2015
Each table is valid for the maximum wind listed at the top of the table and independent of wind direction.
All ROTs shown in this section do not require a velocity bias handed to the weapon, so impact angles of
70-90º can be commanded (provided impact azimuth is invalid for 83º or 84º to inhibit sending a velocity
bias to the weapon). The ROTs tables B.11 – B.15 are valid for 0-10 MPH, Omni-directional targets and
for maximum wind speeds of 20, 40, 60, 80 and 100 knots respectively.
205
Boeing Report 15J0089
May 1, 2015
Table B.11 - LJDAM Slant Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 20 Knots
(Slick ADE, 0.70-0.95M)
206
Boeing Report 15J0089
May 1, 2015
Table B.12 - LJDAM Slant Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 40 Knots
(Slick ADE, 0.70-0.95M)
207
Boeing Report 15J0089
May 1, 2015
Table B.13 - LJDAM Slant Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 60 Knots
(Slick ADE, 0.70-0.95M)
208
Boeing Report 15J0089
May 1, 2015
Table B.14 - LJDAM Slant Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 80 Knots
(Slick ADE, 0.70-0.95M)
209
Boeing Report 15J0089
May 1, 2015
Table B.15 - LJDAM Slant Range Release Rule of Thumb for 0 – 10 mph for Winds Up To 100 Knots
(Slick ADE, 0.70-0.95M)
210
Boeing Report 15J0089
May 1, 2015
B.2.3 Low HAT & Dive (0-40 MPH) Slant Range ROT Tables
During Block 9 development, a specific set of tables was requested to address LJDAM employment at
altitudes below 10 Kft HAT and at negative flight path angles. The tables in this section present ROTs for
0 – 40 MPH, omni-directional targets for release altitudes of 6 – 12.5 Kft HAT and dive angles from 0 to
negative 45 degrees. Each table is valid for the maximum wind listed at the top and is independent of wind
direction.
All ROTs shown in this section assume employment with a standard JDAM interface, meaning that
depending on the target speed range, a velocity bias must be handed to the weapon as indicated in the table.
For target speeds of 0-20 MPH, a zero velocity bias is specified and the impact angles command should be
set to 70º. For target speeds of 20 – 40 MPH, a 40 MPH velocity bias is specified and the impact angle
command should be set to 68º (with the azimuth validity set to valid and angle commanded to be the true
target direction). The ROTs tables B.16 – B.19 are valid for 0 – 40 MPH, omni-directional targets and for
maximum wind speeds of 20, 40, 60, and 80 knots respectively.
211
Boeing Report 15J0089
May 1, 2015
Table B.16 - LJDAM Slant Range Release Low HAT ROT for 0 – 40 mph for Winds Up To 20 Knots
212
Boeing Report 15J0089
May 1, 2015
Table B.17 - LJDAM Slant Range Release Low HAT ROT for 0 – 40 mph for Winds Up To 40 Knots
213
Boeing Report 15J0089
May 1, 2015
Table B.18 - LJDAM Slant Range Release Low HAT ROT for 0 – 40 mph for Winds Up To 60 Knots
214
Boeing Report 15J0089
May 1, 2015
Table B.19 - LJDAM Slant Range Release Low HAT ROT for 0 – 40 mph for Winds Up To 80 Knots
215
Boeing Report 15J0089
May 1, 2015
Release
Altitude (ft, Impact Bias Speed Target Speed True Target
MSL) Angle (deg) (mph) (mph) Direction (deg) Mach Footprint Chart
0.75
15,000 70 0.85 Figure B.10
0.95
N/A N/A 0.75
N/A
70 Stationary Stationary 0.85 Figure B.11
Stationary Target
Target Target 0.95
25,000
0.75
90 0.85 Figure B.12
0.95
N/A 0 deg Relative to 0.75
70 No Velocity 15 Weapon Release 0.85 Figure B.13
Bias Heading 0.95
15,000
45 deg Relative to 0.75
68 40 35 Weapon Release 0.85 Figure B.14
Heading 0.95
N/A 90 deg Relative to 0.75
90 No Velocity 15 Weapon Release 0.85 Figure B.15
Bias Heading 0.95
25,000
180 deg Relative to 0.75
83 40 35 Weapon Release 0.85 Figure B.16
Heading 0.95
N/A 45 deg Relative to 0.75
70 No Velocity 15 Weapon Release 0.85 Figure B.17
Bias Heading 0.95
35,000
90 deg Relative to 0.75
83 40 35 Weapon Release 0.85 Figure B.18
Heading 0.95
0 deg Relative to 0.75
10,000 69 60 50 Weapon Release 0.85 Figure B.19
Heading 0.95
0 deg Relative to 0.75
15,000 69 60 60 Weapon Release 0.85 Figure B.20
Heading 0.95
0 deg Relative to 0.75
25,000 69 60 60 Weapon Release 0.85 Figure B.21
Heading 0.95
-45 deg Relative to 0.75
84 60 70 Weapon Release 0.85 Figure B.22
Heading 0.95
35,000
-45 deg Relative to 0.75
69 60 60 Weapon Release 0.85 Figure B.23
Heading 0.95
Table B.20 – List of LJDAM Example Footprints (Slick ADE, Mach 0.70-0.95)
216
Boeing Report 15J0089
May 1, 2015
Figure B.10 – GBU-54 Stationary Target, Altitude = 15 kft, Impact Angle = 70 deg
Figure B.11 – GBU-54 Stationary Target, Altitude = 25 kft, Impact Angle = 70 deg
217
Boeing Report 15J0089
May 1, 2015
Figure B.12 – GBU-54 Stationary Target, Altitude = 25 kft, Impact Angle = 90 deg
Figure B.13 – GBU-54 Moving Target, No Velocity Bias, Altitude = 15 kft, (70 deg Impact Angle
Command), Target Speed = 15 mph
218
Boeing Report 15J0089
May 1, 2015
Figure B.14 – GBU-54 Moving Target, Velocity Bias, Altitude = 15 kft, Bias Speed = 40 mph (68 deg
Impact Angle Command), Target Speed = 35 mph
Figure B.15 – GBU-54 Moving Target, No Velocity Bias, Altitude = 25 kft, (90 deg Impact Angle
Command), Target Speed = 15 mph
219
Boeing Report 15J0089
May 1, 2015
Figure B.16 – GBU-54 Moving Target, Velocity Bias, Altitude = 25 kft, Bias Speed = 40 mph (83 deg
Impact Angle Command), Target Speed = 35 mph
Figure B.17 – GBU-54 Moving Target, No Velocity Bias, Altitude = 35 kft, (70 deg Impact Angle
Command), Target Speed = 15 mph
220
Boeing Report 15J0089
May 1, 2015
Figure B.18 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 40 mph (83 deg
Impact Angle Command), Target Speed = 35 mph
Figure B.19 – GBU-54 Moving Target, Velocity Bias, Altitude = 10 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 50 mph
221
Boeing Report 15J0089
May 1, 2015
Figure B.20 – GBU-54 Moving Target, Velocity Bias, Altitude = 15 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
Figure B.21 – GBU-54 Moving Target, Velocity Bias, Altitude = 25 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
222
Boeing Report 15J0089
May 1, 2015
Figure B.22 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 60 mph (84 deg
Impact Angle Command), Target Speed = 70 mph
Figure B.23 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
223
Boeing Report 15J0089
May 1, 2015
The energy capability curves provide a quick reference to help select release conditions that will ensure
there is a ROT available to pursue a specific target. The curves show the minimum energy (as a
combination of Mach and height above target) required to successfully engage a specific target speed and
target altitude. There are multiple curves on each plot and each represents a maximum wind limit in knots.
The legend describes the target altitude and maximum allowable wind magnitude. The curves are valid for
winds from any direction. In each plot, a valid ROT should exist for any Mach and altitude that is above
and to the right of the applicable curve as shown in Figure C.1. Mach and altitude combinations that are
below and to the left of the curve will not result in a valid ROT due to a combination of things: the
constraints of the ROT table (ex, Omni-directional capability), and limited energy at release to satisfy all
requirements in the tables (i.e. meeting accuracy requirements in all specified wind conditions, target
directions, headings, etc). Knowing the maximum winds and target altitude for a specific mission should
help narrow down the minimum release speeds and altitudes required to engage either slow (0-40 MPH) or
fast (40-70 MPH) moving targets.
The first three energy capability plots, Figures C.1-C.3 show where ROTs exist for targets moving 0-40
MPH in any direction (Omni-directional). Figures C.1, C.2 and C.3 show the results for 0, 5 and 10 Kft
MSL target altitudes, respectively. Figures C.4 - C.6 show where ROTs exist at release altitudes of 20Kft
HAT and above against targets moving 40-70MPH. Note fast mover ROTs are restricted to a tail-chase
constraint of +/- 45 deg, that is, the aircraft heading must be within +/- 45 degrees of the target heading.
Figures C.4, C.5 and C.6 also show results for 0, 5 and 10 Kft MSL target altitudes respectively. Figures
C.7 - C.9 show where ROTs exist at release altitudes of 15Kft HAT and below for targets moving 40-
50MPH. Figures C.7, C.8 and C.9 also show results for 0, 5 and 10 Kft MSL target altitudes, respectively.
Figure C.1 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
0 Kft MSL Target Altitude
224
Boeing Report 15J0089
May 1, 2015
Figure C.2 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
5 Kft MSL Target Altitude
Figure C.3 – Energy Capability Curves for 0-40 MPH Targets, Omni-Directional Target Hdg
10 Kft MSL Target Altitude
225
Boeing Report 15J0089
May 1, 2015
Figure C.4 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º Release
0 Kft MSL Target Altitude
Figure C.5 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º Release
5 Kft MSL Target Altitude
226
Boeing Report 15J0089
May 1, 2015
Figure C.6 – Energy Capability Curves for 40-70 MPH Targets, Tail chase Condition of ±45º Release
10 Kft MSL Target Altitude
Figure C.7 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º Release
0 Kft MSL Target Altitude
227
Boeing Report 15J0089
May 1, 2015
Figure C.8 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º Release
5 Kft MSL Target Altitude
Figure C.9 – Energy Capability Curves for 40-50 MPH Targets, Tail chase Condition of ±45º
10 Kft MSL Target Altitude
228
Boeing Report 15J0089
May 1, 2015
ROT tables for this centered ADE specific manual were tailored to address operator feedback on data
organization. The general goal was to reduce the amount of real-time decision making required during run-
in to successfully employ the weapon. Therefore all ROT tables are broken out for a maximum wind and
are independent of wind direction. Once a maximum wind for the day has been established, an appropriate
table can be selected prior to the mission and winds will not need real-time consideration. Tables are
available that address slow moving (0-40 MPH) and fast moving (40-70 MPH) targets. Block 8 software
improvements have made it possible to compute Omni-directional ROTs for slow moving targets (0-
40MPH). Thus for slow movers, target heading need not be a real-time consideration. ROTs for fast
moving targets (40 -70 MPH) are still restricted to a ±45º tail chase condition.
ROT results shown below are then valid for the maximum wind and target speeds listed at the top of each
table. They are independent of wind direction. The appropriate table for the mission is selected based on the
expected winds that day and expected target speeds to engage. Each table provides release ground range
distances for release altitudes of 10, 12.5, 15, 20, 25, 30 and 35 Kft HAT and for Mach points of 0.70, 0.75,
0.80, 0.85, 0.90 and 0.95. For each altitude and Mach combination, a release ground range distance is listed
for target altitudes of 0, 5 and 10 Kft MSL. No ROTs were provided for release altitudes above 35 Kft
MSL. Release altitudes at 40 Kft and above were not identified as high priority and data generation was
concentrated on lower altitude employment.
Under the target altitude columns, there is a release ground range distance to target with a tolerance
denoted by the symbol “±”. So for example a release ground range distance of 3 nmi ± 1 nmi would
represent a 2 nmi long ROT box that is valid from 2 to 4 nmi downrange to the target. For a ROT to be
considered valid it should have a minimum of ±0.3 nmi of depth. Cases where the ROT depth is less are
provided in the table but shown in red to help with interpolation between ROTs. Cases where no ROT
exists for that condition show up as “NoROT” in the table. The cross range tolerance on the ROT box is a
minimum of ± 0.3 nmi wide. The ROT models are designed for a weapon accuracy of 5m CEP for 0-
40MPH targets and 6m CEP for 40-70 MPH targets. They also assume that the achieved weapon impact
angle is 30-90º. All ground range release distances are only valid for the impact angle and impact azimuth
commands listed in the third and fourth columns. Note that the ROT boxes (i.e. the ROT +/- the tolerance)
for each case represents the un-conservative, maximized window for which the weapon can be employed.
Similar to JDAM baseline LARs, for the greatest probability of success it is advised to release as close to
the ROT center as possible.
The following three sections, C.2.1-C.2.3, show the generalized ROT tables and two additional sets of
tables that are focused on special employment circumstances. Section C.2.1 shows the generalized ROT
tables for slow (0-40 MPH) and fast (40-70 MPH) moving targets. Section C.2.2 shows ROT tables for
employment against very slow movers (0-10 MPH) and is intended to supplement the general ROT tables
in order to open up capability for this specific condition.
C.2.1 Slow (0-40 MPH) and Fast (40-70 MPH) Movers ROT Tables
For the slow mover tables (0-40 MPH), the impact angle command has two settings depending on the
estimated target speed. If the target is moving very slow, approximately 0-20 MPH, the ROT can be used
without passing a velocity bias to the weapon and impact angle commands of 70-90º can be used. Impact
azimuth command is not required and if not specifically needed, should be set as invalid. If a target is
moving in the range of 20-40 MPH, the ROT can be used by commanding an impact angle of 68º or 83º
which passes a 40 MPH velocity bias to the weapon. In this case the impact azimuth command should be
valid and used to specify the target heading at release (See Table 8.9 – Block 9 Manual Mode Velocity Bias
Logic Summary).
229
Boeing Report 15J0089
May 1, 2015
There is no significant change in weapon performance at a target speed breakpoints found in the table and
some degree of overlap is acceptable. For example at 20 MPH, some overlap exists where either impact
angle command can be used, that is, one that specifies no velocity bias (70-90º) or one that specifies a 40
MPH velocity bias (68º or 83º). When choosing the appropriate impact angle command and velocity bias,
the weapon performance is optimized by passing the weapon the closest approximation possible to the
target’s true speed. Each ground range release distance shown in the table is valid for either case (i.e., either
using 70-90º impact angle command with an invalid azimuth command for 0-20 MPH targets or a 68º/83º
impact angle command with a valid azimuth command defining the target heading for 20-40 MPH targets).
Similarly for the fast mover tables (40-70 MPH) at high HAT release conditions of 20-35Kft HAT, there
are two settings for impact angle command. For targets moving 40-60 MPH, the ROTs can be used by
commanding an impact angle of 68º or 83º (40 MPH bias) and for targets moving 60-70 MPH, the ROTs
can be used by commanding an impact angle of 69º or 84º (60 MPH bias). In either case, the impact
azimuth command should again be valid and used to specify the target heading at release.
For low HAT release conditions of 10-15Kft, the ROTs in the fast mover table are only provided for target
speeds up to 50 MPH. At low release altitudes performance degrades against 50-70 MPH targets. The ROT
capability is much greater by only engaging targets up to 50 MPH at this altitude. For these low HAT
conditions engaging target speeds of 40-50 MPH, the ROTs can be used by commanding an impact angle
of 68º or 83º (40 MPH bias) and specifying target heading via the azimuth command.
Note that all downrange distances shown are distances to the target at weapon separation, not weapon
pickle. An additional downrange increment should be added based on the specific aircraft pickle duration
and aircraft inertial speed at release.
Tables C.1 - C.5 provide the Rules of Thumb for Omni-directional targets of speeds between 0-40 MPH for
wind limits of 20, 40, 60, 80, and 100 knots respectively. Tables C.6 - C.10 show the Rules of Thumb for
targets of speeds between 40-70 MPH, subject to a ±45º tail chase condition, for wind limits of 20, 40, 60,
80, and 100 knots respectively.
To reduce the amount of real-time lookup aircrews must accomplish, the intent here is that they select the
appropriate table from below prior to the mission based on winds that day and anticipated target speeds.
For example if winds are 30-40 knots and target speeds are expected to be 0-40 MPH, Table C.2 would be
selected as that data is for slow movers and valid up to maximum wind speeds of 40 knots. (As noted, all
the ROT tables below are independent of wind direction).
Once the table is selected the aircrew can mission plan their release altitude and airspeed based upon the
capability of the aircraft and weapon at the expected target altitude. For slow movers, the operator should
only have to check the release ground range and set the impact angle commands to employ the weapon. To
engage fast moving targets the aircraft would also need to be in a tail chase condition.
In the unique case where the target is fixed or moving approximately 20 MPH or slower, it is possible to set
the impact angle command anywhere between 70-90º prior to run on the target (bearing in mind that impact
azimuth command should be invalid for impact angle commands of 83º and 84º to inhibit sending a
velocity bias to the weapon). Then there is only one real-time parameter to consider - the correct release
ground range distance to the target.
230
Boeing Report 15J0089
May 1, 2015
Table C.1- LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph For Winds Up To 20
Knots (Centered ADE, 0.70-0.95M)
231
Boeing Report 15J0089
May 1, 2015
Table C.2 - LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph For Winds Up To 40
Knots (Centered ADE, 0.70-0.95M)
232
Boeing Report 15J0089
May 1, 2015
Table C.3 - LJDAM Ground Range for 0 – 40 mph For Winds Up To 60 Knots
233
Boeing Report 15J0089
May 1, 2015
Table C.4 LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph For Winds Up To 80 Knots
(Centered ADE, 0.70-0.95M)
234
Boeing Report 15J0089
May 1, 2015
Table C.5 - LJDAM Ground Range Release Rule of Thumb for 0 – 40 mph For Winds Up To 100
Knots (Centered ADE, 0.70-0.95M)
235
Boeing Report 15J0089
May 1, 2015
Table C.6 - LJDAM Ground Range for 40 – 70 mph For Winds Up To 20 Knots
236
Boeing Report 15J0089
May 1, 2015
Table C.7 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph For Winds Up To 40
Knots (Centered ADE, 0.70-095M)
237
Boeing Report 15J0089
May 1, 2015
Table C.8 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph For Winds Up To 60
Knots (Centered ADE, 0.70-095M)
238
Boeing Report 15J0089
May 1, 2015
Table C.9 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph For Winds Up To 80
Knots (Centered ADE, 0.70-095M)
239
Boeing Report 15J0089
May 1, 2015
Table C.10 - LJDAM Ground Range Release Rule of Thumb for 40 – 70 mph For Winds Up To 100
Knots (Centered ADE, 0.70-095M)
240
Boeing Report 15J0089
May 1, 2015
Each table is valid for the maximum wind listed at the top of the table and independent of wind direction.
All ROTs shown in this paragraph do not require a velocity bias handed to the weapon, so impact angles of
70-90º can be commanded (provided impact azimuth is invalid for 83º or 84º to inhibit sending a velocity
bias to the weapon). The ROTs tables C.11 – C.15 are valid for 0-10 MPH, omnidirectional targets and for
maximum wind speeds of 20, 40, 60, 80 and 100 knots respectively.
241
Boeing Report 15J0089
May 1, 2015
Table C.11 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph For Winds Up To 20
Knots (Centered ADE, 0.70-0.95M)
242
Boeing Report 15J0089
May 1, 2015
Table C.12 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph For Winds Up To 40
Knots
243
Boeing Report 15J0089
May 1, 2015
Table C.13 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph For Winds Up To 60
Knots (Centered ADE, 0.70-0.95M)
244
Boeing Report 15J0089
May 1, 2015
Table C.14 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph For Winds Up To 80
Knots (Centered ADE, 0.70-0.95M)
245
Boeing Report 15J0089
May 1, 2015
Table C.15 - LJDAM Ground Range Release Rule of Thumb for 0 – 10 mph For Winds Up To 100
Knots (Centered ADE)
246
Boeing Report 15J0089
May 1, 2015
247
Boeing Report 15J0089
May 1, 2015
Figure C.10 – GBU-54 Stationary Target, Altitude = 15 kft, Impact Angle = 70 deg
Figure C.11 – GBU-54 Stationary Target, Altitude = 25 kft, Impact Angle = 70 deg
248
Boeing Report 15J0089
May 1, 2015
Figure C.12 – GBU-54 Stationary Target, Altitude = 25 kft, Impact Angle = 90 deg
Figure C.13 – GBU-54 Moving Target, No Velocity Bias, Altitude = 15 kft, (70 deg Impact Angle
Command), Target Speed = 15 mph
249
Boeing Report 15J0089
May 1, 2015
Figure C.14 – GBU-54 Moving Target, Velocity Bias, Altitude = 15 kft, Bias Speed = 40 mph (68 deg
Impact Angle Command), Target Speed = 35 mph
Figure C.15 – GBU-54 Moving Target, No Velocity Bias, Altitude = 25 kft, (90 deg Impact Angle
Command), Target Speed = 15 mph
250
Boeing Report 15J0089
May 1, 2015
Figure C.16 – GBU-54 Moving Target, Velocity Bias, Altitude = 25 kft, Bias Speed = 40 mph (83 deg
Impact Angle Command), Target Speed = 35 mph
Figure C.17 – GBU-54 Moving Target, No Velocity Bias, Altitude = 35 kft, (70 deg Impact Angle
Command), Target Speed = 15 mph
251
Boeing Report 15J0089
May 1, 2015
Figure C.18 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 40 mph (83 deg
Impact Angle Command), Target Speed = 35 mph
Figure C.19 – GBU-54 Moving Target, Velocity Bias, Altitude = 10 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 50 mph
252
Boeing Report 15J0089
May 1, 2015
Figure C.20 – GBU-54 Moving Target, Velocity Bias, Altitude = 15 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
Figure C.21 – GBU-54 Moving Target, Velocity Bias, Altitude = 25 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
253
Boeing Report 15J0089
May 1, 2015
Figure C.22 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 60 mph (84 deg
Impact Angle Command), Target Speed = 70 mph
Figure C.23 – GBU-54 Moving Target, Velocity Bias, Altitude = 35 kft, Bias Speed = 60 mph (69 deg
Impact Angle Command), Target Speed = 60 mph
254