Jump to content

Using the INS for precission bombing


Zeus67

Recommended Posts

The INS can be used for precision bombing of fixed targets on the ground.

The use of the INS simplifies targeting calculations, specially the target altitude (ground altitude).

INS should not be used for bombing moving objects.

 

REQUIREMENTS:

1. A Flight plant that includes the target area.

2. A waypoint (BUT) that is to be used as the bombing run inital point (IP).

3. An offset (BAD) to the IP that is where the target is located.

 

Note: As you can see the target is NOT on the waypoint but offset to it.

 

The target offset can be set as follows:

a. In x/y coordinates by using ΔL/ΔG:

ΔL = Distance difference between the IP Latitude and the BAD Latitude expressed in kilometers to the North or South. (True North is used)

ΔG = Distance difference between the IP Longitude and the BAD Longitude expressed in kilometers to the East or West. (True North is used)

b. In polar ρ/θ (Rho/Theta) coordinates:

ρ (Rho) = distance to the BAD position from the IP expressed in Nautical Miles.

θ (Theta) = True North Bearing from the IP towards the BAD.

c. ΔAlt is required.

ΔAlt = Altitude difference between the IP altitude and the BAD altitude:

+ will add the value to the IP altitude.

- will subtract the value from the IP altitude.

 

NOTE: IP altitude MUST be ground altitude. I.E: The altitude of the ground surface above the sea level at the waypoint position.

 

Procedures:

 

CHECK THE FOLLOWING:

1. Radar is ON and Emitting.

2. Radar Altimeter is ON.

 

BEFORE REACHING THE WAYPOINT/IP

1. Select the weapon that you want to use: BL1/BF1/BF4/BF8/EL1. (See Bomb Codes note)

2. Set Master Arm On. System switches to Ground Attack mode.

3. Check that both TAS and RS are selected.

4. Click on PI (Point Initial) button in the PCA. This will designate current waypoint as the IP.

5. The following cues will appear on the HUD:

- A diamond at the bottom of the HUD for IP position update purposes (Radar needs to be in TAS for this option. The diamond represents the radar LOS while in TAS mode)

- Normal NAV cues: "House" track error cue and "Cross" position cue when distance is below 10 NM.

- HSI will display bearing and distance to IP.

6. Update IP position by using the diamond to determine distance to IP (See TAS Position Update Note). HUD will display radar range to IP. You can keep updating IP position as many times as you wish to increase accuracy.

7. IF BL1/EL1 were selected, wings will appear on the FPM --O-- after the 1st IP position update. The wings will provide steering cues towards the BAD.

8. BAD, REC and VAL lights turn on in the PCN when IP is selected. DO NOT CLICK ON VAL UNTIL AFTER WEAPONS RELEASE OTHERWISE TARGETING CALCULATIONS WILL BE OFF.

9. Fly towards the IP by following NAV cues.

 

OVERFLYING THE WAYPOINT/IP

1. HUD radar diamond disappears.

2. Radar range is replaced by range to target (BAD).

2. NAV cues shift towards BAD position.

4. HSI will display bearing and distance to BAD.

 

WEAPONS RELEASE:

1. BL1/EL1 - CCRP:

1.1. Release cues appear in the HUD when in range for pull up.

1.2. Pull UP with full aft stick for max range release. The later/ the slower the pull up is, the closer will the release happen and the lower will be the release angle.

1.3. Press the trigger for weapons release consent.

1.4. Keep the wings level with your FPM during the climb --o--

1.5. The bombs will be automatically released when the release cue cross the target cue (FPM).

1.6. Release the trigger.

2. BF1/BF4/BF8 - CCIP

2.1. Align the CCIP with the target "Cross".

2.2. Press the trigger when the CCIP cue is over the "Cross"

AFTER WEAPONS RELEASE

1. HUD returns to IP designation mode.

- HUD NAV cues point towards the IP.

- HSI will display bearing and distance to IP.

2. Click on VAL por INS position update if desired.

3. Set Master Arm Off to return to NAV mode.

4. PCN BAD, REC and VAL lights turn off.

 

NOTES:

Bomb Codes:

BL1 = Mk-82

BF1 = Mk-82S Snakeye

BF4 = BLG-66 Belouga (Mk-20 Rockeye stand-in)

BF8 = BAP-100

EL1 = GBU-12, GBU-16, GBU-24

 

TAS Position Update:

To update the IP position you must:

1. Place the diamond over the IP true position. The Cross can be offset to it.

2. Click on the Radar Position Update HOTAS Key. The INS will update the IP position. Cross will center on the IP.

3. PCN Display will show:

3.1: If parameter knob is in ΔL/ΔG, the distance (Km) to the IP in x/y format.

3.2: If parameter knob is not in ΔL/ΔG, the distance in NM and the bearing to the IP.

4. DO NOT CLICK ON VAL. The system automatically uses this distance for target calculation.

 

Example: The IP is located on top of a water tower. The HUD Cross is located away from the tower. Place the tower on the diamond and click on radar position update. The cross will be now centered on the water tower.

 

ATTENTION: If for any reason the radar is not available, the INS will extrapolate range to IP based on radar altimeter values with subsequent loss of precision.


Edited by Zeus67

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

  • Replies 162
  • Created
  • Last Reply

Top Posters In This Topic

Awesome! Will try it out tonight.

 

I'm sorry, this won't be ready until next week. :book:

 

I posted this so you can start polishing your INS editing skills and how to create Flightplans, including Offsets.

Offset navigation will be available on tomorrow's release.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

Thanks, Zeus!

Mission: "To intercept and destroy aircraft and airborne missiles in all weather conditions in order to establish and maintain air superiority in a designated area. To deliver air-to-ground ordnance on time in any weather condition. And to provide tactical reconaissance imagery" - F-14 Tomcat Roll Call

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

So is TAS working now? I asked several times but fellow forumers all said that TAS hasn't been implemented yet.

Zeus, could you please clarify?

 

TAS should be working on this release, otherwise on the next. ED fixed the TAS radar problem on developer's version but I am not sure if the fix is available yet for release.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

:cheer3nc::cheer3nc::cheer3nc:

[sIGPIC][/sIGPIC]

 

Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.

Link to comment
Share on other sites

The target offset can be set as follows:

a. In x/y coordinates by using ΔL/ΔG:

ΔL = Distance difference between the IP Latitude and the BAD Latitude expressed in
kilometers
to the North or South. (True North is used)

ΔG = Distance difference between the IP Longitude and the BAD Longitude expressed in
kilometers
to the East or West. (True North is used)

b. In polar ρ/θ (Rho/Theta) coordinates:

ρ (Rho) = distance to the BAD position from the IP expressed in
Nautical Miles
.

θ (Theta) = True North Bearing from the IP towards the BAD.

c. ΔAlt is required.

ΔAlt = Altitude difference between the IP altitude and the BAD altitude:

+ will add the value to the IP altitude.

- will subtract the value from the IP altitude.

Looks great, thanks Zeus!

 

But some questions:

ΔL/ΔG in kilometers but ρ in nautical miles? That is not a typo?

And Δalt is in feet? meters?

Link to comment
Share on other sites

Looks great, thanks Zeus!

 

But some questions:

ΔL/ΔG in kilometers but ρ in nautical miles? That is not a typo?

No, it is not.

 

ΔL/ΔG is designed to be used when contacting ground troops. Their maps use the metric system. So they will tell you the offset in kilometers.

For example: "Your target is located 20 kilometers to the north and 35 kilometers to the east of waypoint bravo".

 

Rho/Theta is designed to be used when contacting air controllers. They use nautical miles so they will give you distance and bearing.

For example: "Your target is 20 NM at bearing 138 from waypoint delta".

 

And Δalt is in feet? meters?

You can enter it on either one.

Left LCD = Δalt in feet.

Right LCD = Δalt in meters.

 

The INS store this value in meters no matter what unit you use.

 

Only Rho is stored as NM.


Edited by Zeus67

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

If you don't mind me asking Zeus, I know it's little offtopic but I wonder if you know anything about making Landing waypoints with INS in flight ... is it at all possible or was it only done via flight plan and Data Cartridge?

 

It will be possible, but you will have to wait after INS precision bombing

  • Like 1

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

Selecting ΔL/ΔG ρ/θ creates a new waypoint?

If i have 4 waypoints in my flight plan and wan't to create an offset

waypoint related to waypoint 3, how do i do that?

Set PREP to 3, fill the ΔL/ΔG or ρ/θ and RAlt values and then what?

Will be a 5 waypoint created? And to navigate to this should i also

chose the respective mode on the HSI ?

Link to comment
Share on other sites

Selecting ΔL/ΔG ρ/θ creates a new waypoint?

If i have 4 waypoints in my flight plan and wan't to create an offset

waypoint related to waypoint 3, how do i do that?

Set PREP to 3, fill the ΔL/ΔG or ρ/θ and RAlt values and then what?

Will be a 5 waypoint created? And to navigate to this should i also

chose the respective mode on the HSI ?

 

No. An offset does not create a new waypoint. It just shifts the navigation from the waypoint position to another position determined by the offset values.

 

In your 4 waypoints flight plan.

 

To create an offset (BAD) for WP3 you must:

 

1. Set PREP to 03

2. Enter either ΔL/ΔG or ρ/θ

3. Enter ΔALT.

 

To activate the WP3 offset, you must:

 

1. Set DEST to 03

2. Click on the BAD button in the PCN.

 

The NAV cues will shift to the offset position.

Also, automatic waypoint update, if active, is disabled while the BAD is active.

 

When doing bombing runs with the INS you do not click on the BAD button in

the PCN but on the PI button in the PCA. That way both the waypoint and its BAD will be secuentially activated.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

I'm going to need a video tutorial for dummies, but once I see it I get it and practice practice practice until I'm quite comfortable with it. Thanks so much for putting your heart and soul into this project, it"s already paying off whilist bringing new and interested people to the DCS world. Pat yourselves on the shoulder Razbam Team and pour a round, you deserve it. Cheers.

X570S AORUS PRO AX MOTHERBOARD, AMD Ryzen 7 5800X3D 8-core Processor, GIGABYTE GEFORCE RTX 3090 TI, 64GB DDR4(Corsair Vengeance LPX), DARK ROCK PRO 4 250W TDP Heatsink, Corsair AX1600i Power Supply,  2TB SSD, Windows 10 64 Bit  VR: HP Reverb G2, VIRPIL: VPC Constellation ALPHA Prim[R], VPC MongoosT-50CM3 Throttle, VPC MongoosT-50CM3 Base

Link to comment
Share on other sites

Is there any way to fly direct to a BAD offset point without overflight of its mother waypoint first?

 

If BAD is entered dL/dG format will rho/theta values update to match and vice versa?

 

How is INS position update done otherwise?

Link to comment
Share on other sites

Is there any way to fly direct to a BAD offset point without overflight of its mother waypoint first?

For normal navigation? Yes. All you have to do is click on the BAD button in the PCN and follow the NAV cues in the HUD.

 

For a bombing run? No. The waypoint is the IP and you must overfly it so the INS knows that you are in your attack run.

 

If BAD is entered dL/dG format will rho/theta values update to match and vice versa?

No. dL/dG entry is independent from Rho/Theta.

 

The INS checks first for dL/dG and then for Rho/Theta, actually it only checks if Rho is greater than 0.

 

If dL, dG and Rho are 0 then there is no BAD and the system does nothing.

 

How is INS position update done otherwise?

Check the manual, normal INS position update is detailed there.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

Great Zeus.....I see you mention the GBU, but this type of bombs always needs laser guidance, correct?

 

Yes, but for the M-2000C the GBUs are just another type of slick iron bombs. That is why it groups all of them as EL1.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Link to comment
Share on other sites

For normal navigation? Yes. All you have to do is click on the BAD button in the PCN and follow the NAV cues in the HUD.

 

For a bombing run? No. The waypoint is the IP and you must overfly it so the INS knows that you are in your attack run.

 

Do I get that right?: You can store one offset (BAD) for each waypoint in your flight plan? I know, having an offset for every waypoint doesn't make sense in practical use, but in theory that is how it works?

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

 

DCS Panavia Tornado (IDS) really needs to be a thing!

 

Tornado3 small.jpg

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...