Wednesday Fibre: F/A-18C Loft Bombing Mission (screenshot heavy)

F/A-18C Loft Bombing Mission

This is a post mission report for a Loft bombing mission designed by near_blind for our “Wednesday Night Fibre” multiplayer group.

Dramatis Personae

Personality Nose Markings Role Aircraft Origin
@near_blind 302 Mission Lead Eisenhower (CVN-69)
@Bogusheadbox 25 Life Lesson Coach Eisenhower (CVN-69)
@DeadMeat 301 Alternative Flight Stylist Eisenhower (CVN-69)
@chipwich 311 Doesn’t Wanna Loft Eisenhower (CVN-69)
@Andrew116 311 Alternate 311 SAM decoy Eisenhower (CVN-69)
@Fridge 313 RCAF CF-188 Fanboi Al Minhad

unDramatis Personae: Absent from the Mission for ‘Reasons’

Personality Nose Markings Role Aircraft Origin
@fearlessfrog n/a Airport Integrity Checker n/a
@Tankerwade n/a Squadron Designate Cold/Flu Lad n/a
@AeroMechanical n/a Frequently Late Airman n/a

Mission Brief

We are all gonna die. It’s always safe to start off that way because it is safe to set your goals and keep your expectations low, but when it isn’t, oh man can you feel that surprise! :slight_smile:

Our mission was relatively simple; at least it will ‘sound’ simple but for most of us who are not near_blind, and who do not practice these things very much, it will be more complex to actually execute. We are to enter Iranian territory to the north, circle around and approach the Bandar Abbas International airbase from the north, attack and destroy via loft bombing some support buildings in an elaborate international insurance fraud scheme.

Here are the way-points handed out. We would use these map markings to generate Lat/Lon way-points that we would enter into the 18C computer and use on our own terms. I modified the way-points that were already in the system while others added new way-points.

Target assignments were distributed as well. Again, using the same systems above, we entered these into the system manually. near_blinds target was the building between those of chipwich, DeadMeat and I (Fridge).

We also determined a flight assembly point over Sirri Island were we could all meet up and push to way-point #1.

Loft Bombing

The loft bombing is critical. As you would expect, the airbase is defended and overflying it is generally consider ‘dangerous’ or at least that is what the intelligence analysts who were assigned during the planning have been telling everyone. Who knows? It’s not like near_blind likes to hide surprises in his missions, it’s just not normal for him to tell us about them.

From: Basic Emplyment Manual AFTTP 3-3 Vol 5;

So the Loft Bombing is, again, relatively simple. Let me check my notes from last Wednesday because even though it’s ‘simple’, I’m old enough to need notes and reminders. Here is what I wrote:

Transcription: MIL → 6nm → AB + 4G/45° → Pickle

In long form: Push in to the target with proper line-up at MIL power, at 6nm go to afterburner, pull 4G on the jet up to 45° nose high, when release cue moves down then press and hold pickle button, roll away, dive and run fast like across the desert.

This is easy to say but hard to remember in the moment. It gets you all tunnel visioned during the run in and loft while trying to keep everything else going in the right direction.

Mission Execution

Taking off from the carrier is sexy. Really sexy. I mean, look at it!

[Fanboi rant]I know a lot of people see all the negatives in this game and I seriously can not understand that attitude. I’d say this all throughout this AAR but how can you not look at what we have and marvel that we have it!?! Is it perfect? No. Will it ever be perfect? Ha! No. What we have is an amazing feat of development and engineering that does not get the respect and appreciate that it is due.[end Fanboi rant]

There is not enough space on the carrier for us to all launch from without a significant carrier deck-dance, so I elected to take off from Al Minhad AB instead and save us (mainly me) the confusion. I tend to dislike crowds anyway.

We delayed at this point to away the arrival of our fearless (frog) leader but he was detained by an integrity check that was difficult to diagnose when you are in VR (and get that nice headache inducing hourglass and crosseyed (to me) static display). That gave us all time to go through the waypoint entries and set up the weapon profiles.

Soon enough it was time to get underway. I know it was probably frustrating for fearlessfrog to try working through his issue while we were all entering coordinates and profiles and it probably felt like we were abandoning him but I hope not.

I pre-pologise (a preloaded apology before I start doing something that I probably should apologize for after it is done): prepare for some DCS 2.5 F/A-18C screenshot spam. Seriously it’s hard to edit these down to just a few.

Form-up image dump - click to expand

We all arrived over Sirri Island in one piece and pushed on. I was very slow in rejoining on the formation on the push to way-point 1. I was nursing my thrust (and gas) but was able to catch this picture.

It’s hard to see but that was #311 (Andrew116) impacting #301 (DeadMeat) in dramatic fashion through the fault of, well, no one really. There was a lag spike that caused #311 to become stationary and slide back into #301.

Collision frame sequence - click to expand

Doh! Down two aircraft in the middle of ingress is a PitA, not for those who survive but it brings a abrupt end to a mission for those who put all that time into getting to that point and now can’t continue. Sorry guys! We pressed on!

At least there is only one #311 aircraft now, so it’s easier to figure out who I am looking at.

We pressed on from way-point 1 to way-point 2.

Just prior to reaching way-point 2 we switched to a trail formation which would make the dive to the deck easier and less prone to pilot error induced collisions.

The roll into the dive was spectacular!

Additional Roll-In Shots - click to expand

The run from way-point 2 to the IP was fast and low as we made sure that none of us was going to draw swift attention from any SAM assets that would make a guess at our plot.

Low Level shots - click to expand

It was here that I made my mistake. I had been planning to drop the tanks to give me a little more ‘freedom’ on the IP (less drag, weight, etc). Unfortunately, I selected the correct stations for my ‘Selective Jettison’ but I hit the wrong button.

No Fridge! Don’t hit the yellow button! Replay me didn’t listen.

Doh. Well, now I had a disturbingly clean aircraft to strike at the airfield with. I guess that is why we brought so many extra jets on the mission. We are down to 3 target-effective jets at this point. :frowning:

More 'Run-In' shots - click to expand

near_blind hit his loft trigger distance first.

Bogus was next. I was still following through on my plan even though I had that dangerously clean jet. I was ahead of him by a smidge and judged my rollout/dive away point while Bogus pressed on. I was hoping that I could at least get the attention of any SAM assets that might be watching our airshow.

Sure enough. Someone was down there and they were hungry for western jets!

near_blind announced a SAM (SA-6) shot shortly after this.

You can see near_blind in this shot just off to the right of the SAM-smoke-elbow. My (preemptive) flares can be seen in the upper right corner.

Bogus finished his loft. Delivery on it’s way!

We did end up drawing a Tunguska shot as well. Upper arc of flares were mine. Lower and to the left are those of near_blind. Not pictured: at this point the SA-6 had tried to lead near_blind far enough that it impacted the ground just off the runway of Bandar Abbas International.

It had me targeted but doesn’t have the smash to get close enough as near_blind sprints along the desert. Out of frame, Bogus is behind finishing his loft and chipwhich is beginning his run in to the target.

near_blinds bombs hit close to their target (off, likely, do to the dynamic weather and temperature calculations that are not currently handled by the 18C’s computer.

Bongus had his bombs hit just long as well. All in all, both profiles look good and were executed good.

We egreseds as fast as we can.

chipwich was, however, still over the target. A couple of Tunguska shots can’t make the final turn to follow him.

Or maybe they were distracted? You be the judge but I account the misses to his superior jet handling.

Now came the real test. Instead of the in-close Tunguska shots, the SA-6 had gotten mad and after some yelling among the crew over whose fault it was that the stations were not manned in time, they elected to try to take their revenge out on chipwich.

That angle was not looking good.

Not good at all.

Sorry chipwich! We pressed on to RTB reporting no chute in sight.

Bogus looked goof (that’s a typo but I’m gonna leave it :slight_smile: ) on the egress.

It was all quiet until our AWACS controller (now Deadmeat) called out a pair of bandits lifting off from Tunb Kochak or Tunb Island AFB. We turned nose hot and worked to get the air-to-air systems up and running. Well I did, as a expect near_blind and Bogus were already properly configured.

Pressing on to the RWR contacts, Bogus picked up the challenging tones from another SA-6 along the cost. He was forced defensive.

More Defensive shots - click to expand

near_blind and I continued to press on to the bandits. I had trouble getting them on the radar at the ranges near_blind was able to, likely because of inexperience and me not understanding HRF, etc.

We launched while Bogus maneuvered clear of his problems.

The MiG-23’s were fast! They detected the launches and turned tail. Unfortunately it looks like near_blind and I had fired on the same target.

The remaining -23 had an interest in me. A potentially fatal interest.

I picked up the launch and appropriately freaked out. I put some G’s on the jet (capital G’s) and pump chaff. I got lucky and the maneuvering paid off, robbing the Apex (R24R) of it’s energy near the end of it’s range.

Bogus took a shot on the closest offensive guy while near_blind pulled in bind him for a follow-up shot. Both hit but near_blind had the kill with the follow-up shot.


Meanwhile, the remaining MiG-23 runner turned back into the fray. Bogus and near_blind were able to follow up on this bandit quickly. I was struggling to get my situational awareness under control and get in the general area of the engagement, but it proved unnecessary to the outcome. near_blind shot a AIM-9M off that damaged the bandit.

Finished off by a guns kill while Bogus’s AIM-9M shot goes blind off of the rail.


Nicely done! We pushed on to the boat.

near_blind in the pattern with chipwich doing some practice trapping … and maybe giving the carrier a nice black smoke trail; really, he was afraid we wouldn’t make it back and decided to ‘mark the target’ for us.

Bogus was next.

Took him a moment to remember that you had to let the engine spool down and let the wire pull you back a little before it would disengage :slight_smile:

I was last in the pattern. Started to get some anxiety with all of those eyes on me!

I was all over the ball but I managed to salvage the approach and got her down.


I would call it a partially successful mission. We hit the target but we had a lot of ‘mission casualties’ along the way. I am glad that everyone was able to make it and I hope we had as much fun as possible considering the difficulties that we encountered.

Our Bomb Lofting Effectiveness

From looking at the TacView track, here is what I can find about our bomb effectiveness. This was more time consuming than I hoped :slight_smile:

Here is the target plan again:

And my notes at the start of the mission:

Going back into the DCS mission editor, it looks like the targets were:
near_blind: 27 14’ 36" N - 056 23’ 04" E
Bogusheadbox: 27 14’ 38" N - 056 23’ 15" E
Fridge: 27 14’ 39" N - 056 23’ 66" E
DeadMeat: 27 14’ 42" N - 056 23’ 02" E
chipwich: 27 14’ 37" N - 056 22’ 59" E

@near_blind’s loft start (@near_blind at the top, @Bogusheadboxoff to the left and @Fridge off to the right)

@Bogusheadbox’s loft start:

@near_blind’s impact point: (27 14’ 34" N - 056 23’ 07" E) (Right green dot is @DeadMeat’s target):

Impacted at or near the end of the pink arrow:

@Bogusheadbox’s impact point: (27 14’ 33" N - 056 23’ 14" E) (Centre green dot is @DeadMeat’s target, Purple dot is @Fridge’s target and the right green dot is @Bogusheadbox’s target):

Impacted at or near the end of the pink arrow:

Using this handy calculator: Calculate distance and bearing between two Latitude/Longitude points using haversine formula in JavaScript

@Bogusheadbox was ‘off’ from my measurement in DCS by 185m

near_blind noted that the weather conditions were likely not accounted for my the bombing computers in the F/A-18C (ie: not modeled yet) and that likely accounts for the bombing runs to appear long.



Nice! So is this Wednesday thing a regular event?


Wow, super in depth AAR.
NICE ONE. :f111:


Probably the most Canadian thing @Fridge has ever said.

Awesome work on the AAR.


Beautiful AAR @Fridge - nice job.

Next week my aircraft will have integrity! :slight_smile:


Nice write up. I’ll be back in the fight soon…




With the Mig-21 and a (fake) nuke you don’t have to be as accurate…just say’n :wink:

Pretty good hits!


Awesome AAR!


LOL…that’s awesome.

What a great AAR…! One of the best I’ve ever read. And sooooo much excitement!

I’ll try to get up to speed to. Give me another week to push some articles out…




Did you get all those screens from a track replay by the way?

Fantastic AAR!

1 Like

Off-Topic Question(*) for gallery: I am starting to use DCS tracks a bit more to work out how I died. If I Control+Z etc to speed up time then is it typical that it isn’t actually a replay? I swear sometimes I win a dogfight and then watch the track, speed it up a bit, and then I am showing as died. This is either the multiverse version of DCS or the track isn’t accurate if speed up - which is it?

(*) Our first ever topic derail! :slight_smile:


Tracks, especially client side ones, are notoriously fragile and prone to breaking. Speeding up time exacerbates the problem.


Yeah, that was why I asked because traditionally, very complex track replays don’t usually stay “true” over time and end up going all whacky. I’d be very impressed if @Fridge’s track played back well enough to grab those accurate screens!

The mission we were flying has deceptively few moving parts. The only persistent, moving “ground” units are three naval groups. Everything else is spawned in dynamically by the user, and we only had six clients, seven SAM sites, and two MiG-23s. Still, I’m pretty impressed it stayed true for an hour long flight.


I used to analyze my flying on 104th a lot by replaying the tracks for tacview. What worked best was replaying them at 2x or sometimes 4x speed but no more. if you do that then the simplest track will go haywire!

Actually ya. That’s how I did it. I recorded the entire mission in Shadowplay from my PoV, spending most of the mission with my head in the cockpit trying to hit all the right buttons. For this AAR I then went back to the replay and spent the mission in an outside view looking in (so to speak), and recorded it all again. The track replays have been working well for me as long as I try to not fast-forward to aggressively. I never go faster than having all the things moving smoothly in-game. If it gets chunky there is a high likelihood of it messing up.

I always copy it to a backup location in case things go sideways and I have some small hope that it was the replay action itself that was borked and not the replay recording). That worked for me once. In another instance few years ago when doing either the A2A Teamwork article with @near_blind, I think my replay borked and I had near_blind send me theirs and it worked for longer than mine did (or maybe it was the MiG-21Bis AAR that I never seem to get back to: :slight_smile: ).

Been lucky so far.

1 Like

What you want for that is Tacview. That gives me the best picture of what is going on with regard to observing a fight and what I might have done wrong. It is easy to fast forward, rewind and move around. The tails that it ads to things are great and you can see a lot of stats on the aircraft that are beneficial to understanding what is happening.