| Author |
 Topic  |
|
|
Vosene
United Kingdom
4594 Posts
Status: offline |
 Posted - 01 Mar 2010 : 00:30:15
|
Members who flew as a Flight Lead in the Sunday mission, An Apology, are requested to post a debrief by Tuesday evening.
|
|
|
Blade
NETHERLANDS
202 Posts
Status: offline |
Posted - 01 Mar 2010 : 01:35:07
|
Blue flight
Panther 1 OCA strike
1 - Crowebar
2 - Blade
3 - Earthmover
4 - Medic!
Weapons
1 - 4x AIM-120-C5, 6x BSU-49, 6x BLU107/B
2 - 4x AIM-120-C5, 2x BSU-50, 2x AGM-65G
3 - 4x AIM-120-C5, 12x BSU-49
4 - 4x AIM-120-C5, 4x GBU-22/B, 2x Mk-84
Mission started out a bit hectic with friendly ground units on active runway. Crowebar joined the fence/signclub by hitting a sign, Earthmover had technical difficulties during rampstart. Flight Lead was therefore forced upon Blade and Panther flight remained with 2 aircraft.
Panther flight took off, passed sp2 for sp3 and got a directive to head north as there were still enemy aircraft over the targer area. Once those were cleared, Panther flight headed for sp3 and 4. We were about to turn for the target when we got a Mig-29 spike on the RWR which Medic! and Blade dealt with accordingly.
A total of 4 SA-6 took Blade down so Medic was on his own. Medic managed to knock out the control tower, after valiantly beating all kinds of missiles throwed at him, and shooting down 2 H-6 bombers in the process.
All in all a very challenging mission. It was hard to even scrape a partial success there, even with the abundance of A-G ordnance available. It got quite hard to make out the comms with all the stuff going on.
--------------------------------------------------------
RECORD BEGIN TIMESTAMP 2/28/2010 23:31:46.
Game is Tactical Engagement type Networked
Mission name: An Apology
Mission Type: OCA Strike
Flight Callsign: Panther1
4 Ship Flight
Ac type: F-16A-MLU
Country: Slovenian
FLIGHT EVENTS
Event Blade joined as Panther12 at 04:57:06
Event Crowebar joined as Panther11 at 04:57:12
Event Medic joined as Panther14 at 04:57:15
Event Earthmover joined as Panther13 at 04:57:19
Event Earthmover exited from Panther13 at 05:03:48
Event Crowebar exited from Panther11 at 05:32:05
Event Yugoslavian MiG-29A downed by Medic at 05:43:21
Event Yugoslavian MiG-29A downed by Medic at 05:43:30
Event Yugoslavian MiG-29A downed by Blade at 05:43:31
Event SA6 launched at Blade 05:43:48
Event SA6 launched at Blade 05:43:51
Event Yugoslavian MiG-29A downed by Blade at 05:43:53
Event SA6 launched at Blade 05:44:10
Event SA6 launched at Blade 05:44:13
Event Blade ejected at 05:44:17
Event Blade exited from Panther12 at 05:49:25
Event Yugoslavian Weapon Trailer destroyed by Medic at 05:58:57
Event Yugoslavian H-6 downed by Medic at 06:10:16
Event Yugoslavian H-6 downed by Medic at 06:11:49
Event Aspide-SkyGd launched at Medic 06:15:14
Event Aspide-SkyGd launched at Medic 06:15:19
Event SA14 launched at Medic 06:17:55
Event SA7 launched at Medic 06:18:02
Event Yugoslavian Control Tower destroyed by Medic at 06:18:05
Event Medic landed at 06:29:24
Event Medic exited from Panther14 at 06:29:53
-------------
PILOT SLOT 1:
Human Player: 2Lt. Crowebar
Callsign: Crowebar
Pilot status - OK
Aircraft status - DAMAGED
AA Kills 0
AG Kills 0
AS Kills 0
AN Kills 0
Shoot At 0
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 0
Missed 0
Hit 0
LOADOUT 1: AIM-120C-5
Starting Load 4
Fired 0
Missed 0
Hit 0
LOADOUT 2: BSU-49
Starting Load 6
Fired 0
Missed 0
Hit 0
LOADOUT 3: BLU-107/B
Starting Load 6
Fired 0
Missed 0
Hit 0
LOADOUT 4: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
-------------
PILOT SLOT 2:
Human Player: Maj. Blade
Callsign: Blade
Pilot status - MIA
Aircraft status - DESTROYED
AA Kills 2
AG Kills 0
AS Kills 0
AN Kills 0
Shoot At 4
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 0
Missed 0
Hit 0
LOADOUT 1: AIM-120C-5
Starting Load 4
Fired 2
Missed 0
Hit 2
Event AIM-120C-5 released at 05:42:54 hit MiG-29A - destroyed
Event AIM-120C-5 released at 05:43:28 hit MiG-29A - destroyed
LOADOUT 2: BSU-50
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 3: AGM-65G
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 4: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
-------------
PILOT SLOT 3:
Human Player: 2Lt. Earthmover
Callsign: Earthmover
Pilot status - OK
Aircraft status - OK
AA Kills 0
AG Kills 0
AS Kills 0
AN Kills 0
Shoot At 0
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 0
Missed 0
Hit 0
LOADOUT 1: AIM-120C-5
Starting Load 4
Fired 0
Missed 0
Hit 0
LOADOUT 2: BSU-49
Starting Load 12
Fired 0
Missed 0
Hit 0
LOADOUT 3: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
-------------
PILOT SLOT 4:
Human Player: Lt. Medic
Callsign: Medic
Pilot status - OK
Aircraft status - OK
AA Kills 4
AG Kills 0
AS Kills 2
AN Kills 0
Shoot At 4
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 4
Missed 3
Hit 1
Event 20mm M61 fired at 06:11:39 hit H-6 - destroyed
Event 20mm M61 fired at 06:11:41 miss
Event 20mm M61 fired at 06:11:52 miss
Event 20mm M61 fired at 06:11:57 miss
LOADOUT 1: AIM-120C-5
Starting Load 4
Fired 4
Missed 0
Hit 4
Event AIM-120C-5 released at 05:42:29 hit MiG-29A - destroyed
Event AIM-120C-5 released at 05:42:43 hit MiG-29A - destroyed
Event AIM-120C-5 released at 06:09:21 hit H-6 - destroyed
Event AIM-120C-5 released at 06:10:04 hit H-6 - damaged
LOADOUT 2: GBU-22/B
Starting Load 4
Fired 4
Missed 0
Hit 4
Event GBU-22/B released at 05:50:03 hit Hangar - damaged
Event GBU-22/B released at 05:52:50 hit Control Tower - damaged
Event GBU-22/B released at 05:58:16 hit Taxiway - damaged
Event hit Weapon Trailer - destroyed
LOADOUT 3: Mk-84
Starting Load 2
Fired 2
Missed 1
Hit 1
Event Mk-84 released at 06:04:47 miss
Event Mk-84 released at 06:18:03 hit Control Tower - destroyed
LOADOUT 4: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0 |
 |
|
|
tiag
1417 Posts
Status: offline |
Posted - 01 Mar 2010 : 13:24:13
|
Green flight + Command
Cowboy 1 Intercept
1 - tiag
2 - AI
3 - Mango
4 - AI
Weapons
1 - 6x AIM-120-C5, 3x Bags
2 - 6x AIM-120-C5, 3x Bags
3 - 6x AIM-120-C5, 3x Bags
4 - 6x AIM-120-C5, 3x Bags
The Plan was to T/O and head ASAP toward the enemy air base. The second intercept flight crewed by Griffin and Ballistic would fly parallel to us and engage the enemy air raid together.
The problems started on the ground when we could not taxi properly due to ground units on the rwys and txways. This was particullarly annoying regarding the AI pilots. My number 2 and 4 took off several minutes after I managed to find my way trough so many vehicles. In the future I would suggest that the TE writer check it before and try to avoid this kind of issue.
The second problem was regarding the RWR. Neither Mango nor I managed to make the RWR work. I have been doing ramp starts on the MLU already since 2005 but never say this kind of problem. I turned off my whole jet two times (engines runing) and started everything from the beginning, but no joy. This morning before going to work, I did a fast ramp start just to check whether I did something wrong, but everything was smooth.
Ok, so Mango and I took off without RWR and engaged the 2 flights with 2-ships MIG-29A escorting the SU-25s.
We sorted the first enemy flight correctly and engaged it. My first missile missed, so I shot a second one which downed the MIG. In the meantime, I was unable to communicate with Griffin in the other flight because other flights were using the frequency for less important calls. I could enumerate several but I believe everyone heard the same calls. Unable to coordinate with the other flight on who would be attacking the second flight of 2-ship MIG-29s, and lacking a RWR, they jumped on us and shot us down.
Summing up, apart of my own problems with the RWR:
1) Really bad comms yesterday. Strike flights were taking off and broadcasting the whole time while the intercept flights were engaging 4x-MIG-29As. Later, Magic 1 did several times calls which were totally ignored although the targetd flights were not in action (I was in the channel).
2) Poor mission performance given the air threats (was someone shot with R-77s?). Agree that we lost two F-16s (Mango and I) for a stupid reason, and one blue on blue (Griffin and Ballistic, I think), but the performance of the squad for the threat level was very low. Specially in the context of the SAM threats and how to avoid it.
3) Regarding the TE structure I have a suggestion from the point of view of someone who already wrote good and bad TEs. When you write a TE, you have to keep in mind that very often the package gets disorganized (as yesterday) and the strike flights reach the tgt area very late. If you donīt plan for this possibility, the whole TE ends with the strike flights flying around the tgt area drooping tons of bombs on it and asking the awacs whether the right window of the tower is damaged or not. Ok, I am being sarcastic here, but I would try to constraint the time the strike (and the whole package) has to hit the tgts. You can use a 1) strong enemy intercept/sweep flight at a given time (after that it is impossible to reach the tgt), 2) do not allow updates of human awacs for BDA (this is not real...just recently with UAVs you are able to get some online video feedback on Afghanistan &CIA in CAS missions), 3) or increase the air defenses. What I woud like to see here: ingress, do your job, egress, rtb, just the real stuff.
|
|
|
|
Griffin
UNITED KINGDOM
5051 Posts
Status: offline |
Posted - 01 Mar 2010 : 16:03:35
|
Black and Blue flight
Falcon 1 - Intercept
1 - Griffin
2 - AI
3 - Ballistic
4 - AI
Weapons
1 - 6x AIM-120-C5, 3x tanks
2 - 6x AIM-120-C5, 3x tanks
3 - 6x AIM-120-C5, 3x tanks
4 - 6x AIM-120-C5, 3x tanks
Falcon was fragged to fly in parallel with Cowboy after they had gone north and we had gone south from Brindisi to check for any immediate dangers to the AB.
After this we started to head for SP3, but Cowboy were already busy with contacts and we went in to help. It got messy then with multiple contacts and comms not being good between Falcon and Cowboy, so we didn't really know what each of us was targetting. It was understandable under the circumstances of a) trying to command AI wingmen as well as sorting your own target out and b) Cowboy not being visible to Falcon on HSD and visa versa.
Tiag has mentioned their situation. After that Falcon headed to set up a CAP just west of the SA3 threat circle. Multiple ships were identified off the coast that turned out to be missile ships. More of that in a moment.
Vosene, in Magic 1, advised us that there was a flight SU-27's taking off and heading for us. We turned to engage. The next I knew was that I was running from what I thought was an R-77, but alas no. Ballistic fired at an Su-27 but it must have gone Mad Dog as it went after and hit me.
Shortly after that engagement was finished, thanks largely to Python flight, Ballistic was hit by a missile from the ships. Then the AI went home.
My points agree largely with Tiags:
- SA was not good enough from anyone, definately including me
- Comms were really rubbish
- Flying with AI wingies when you have so much to do is a NO NO!
There is plenty to work on for all of us after that mission.
That said, both flights got a mission success.
A tough mission, particularly early on for us. Nice one Snakebite.
 |
|
|
|
SnakeBite
USA
1732 Posts
Status: offline |
Posted - 01 Mar 2010 : 18:52:20
|
quote:
Originally posted by tiag
3) Regarding the TE structure I have a suggestion from the point of view of someone who already wrote good and bad TEs. When you write a TE, you have to keep in mind that very often the package gets disorganized (as yesterday) and the strike flights reach the tgt area very late. If you donīt plan for this possibility, the whole TE ends with the strike flights flying around the tgt area drooping tons of bombs on it and asking the awacs whether the right window of the tower is damaged or not. Ok, I am being sarcastic here, but I would try to constraint the time the strike (and the whole package) has to hit the tgts. You can use a 1) strong enemy intercept/sweep flight at a given time (after that it is impossible to reach the tgt), 2) do not allow updates of human awacs for BDA (this is not real...just recently with UAVs you are able to get some online video feedback on Afghanistan &CIA in CAS missions), 3) or increase the air defenses. What I woud like to see here: ingress, do your job, egress, rtb, just the real stuff.
- I don't think the TE writer should be considering a mess that could occur because a flight lead's lack of experience. If a flight lead is not too confident to control his flight, then he can hand it over to someone else. Anyone can fly as a flight lead during the weekdays if they need some training.
In my opinion, comms were jammed all the time and that's the main reason behind the losses we had apart from bad SA.
Some pilot's didn't get any warnings on the naval ships because they don't have their RWR set properly for naval units. Naval units RWR switch should be turned on every time your feet are wet.
Regarding ground units, during testing ground units were outside of the runway and taxi ways, if you find another way to test TE's please let me know Tiag?
SnakeBite |
|
|
|
SnakeBite
USA
1732 Posts
Status: offline |
Posted - 01 Mar 2010 : 19:47:34
|
--------------------------------------------------------
RECORD BEGIN TIMESTAMP 2/28/2010 16:27:52.
Game is Tactical Engagement type Networked
Mission name: An Apology
Mission Type: OCA Strike
Flight Callsign: Lobo1
4 Ship Flight
Ac type: F-16A-MLU
Country: Slovenian
FLIGHT EVENTS
Event SnakeBite joined as Lobo12 at 04:55:10
Event Sabre_185th joined as Lobo11 at 04:55:11
Event Tomb joined as Lobo13 at 04:55:14
Event Theron_185th joined as Lobo14 at 04:55:16
Event Yugoslavian Radar destroyed by Tomb at 05:34:24
Event Yugoslavian ZU-23 destroyed by Tomb at 05:40:46
Event Yugoslavian Weapon Loader destroyed by Theron_185th at 05:41:37
Event Yugoslavian Hangar destroyed by SnakeBite at 05:41:49
Event SA7 launched at Sabre_185th 05:41:53
Event SA14 launched at Sabre_185th 05:42:09
Event Yugoslavian Runway destroyed by Sabre_185th at 05:42:11
Event Sabre_185th ejected at 05:42:22
Event Sabre_185th exited from Lobo11 at 05:49:18
Event SA7 launched at Tomb 05:49:31
Event Yugoslavian Hangar destroyed by Tomb at 05:49:40
Event Yugoslavian Su-25 downed by SnakeBite at 05:50:17
Event Aspide-SkyGd launched at Tomb 05:50:22
Event Yugoslavian Su-25 downed by SnakeBite at 05:50:24
Event Yugoslavian Su-25 downed by SnakeBite at 05:50:28
Event Theron_185th ejected at 05:54:26
Event SA7 launched at SnakeBite 05:57:35
Event Yugoslavian Su-25 downed by Tomb at 05:58:09
Event SA14 launched at SnakeBite 05:58:51
Event SA14 launched at SnakeBite 05:58:59
Event SA7 launched at SnakeBite 05:59:03
Event SA14 launched at SnakeBite 06:01:35
Event SA14 launched at SnakeBite 06:01:42
Event SA7 launched at SnakeBite 06:01:47
Event Yugoslavian Hangar destroyed by SnakeBite at 06:01:48
Event Yugoslavian H-6 downed by Tomb at 06:14:27
Event SnakeBite landed at 06:25:24
Event Tomb landed at 06:26:32
Event SnakeBite exited from Lobo12 at 06:26:51
-------------
PILOT SLOT 1:
Human Player: 2Lt. Sabre
Callsign: Sabre_185th
Pilot status - MIA
Aircraft status - DESTROYED
AA Kills 0
AG Kills 0
AS Kills 1
AN Kills 0
Shoot At 2
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 0
Missed 0
Hit 0
LOADOUT 1: Python-4
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 2: AIM-120B
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 3: AIM-120C-5
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 4: BLU-107/B
Starting Load 6
Fired 2
Missed 0
Hit 2
Event BLU-107/B released at 05:42:05 hit Runway - destroyed
Event BLU-107/B released at 05:42:06 hit Runway - damaged
LOADOUT 5: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
-------------
PILOT SLOT 2:
Human Player: 2Lt. SnakeBite
Callsign: SnakeBite
Pilot status - OK
Aircraft status - DAMAGED
AA Kills 3
AG Kills 0
AS Kills 2
AN Kills 0
Shoot At 7
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 0
Missed 0
Hit 0
LOADOUT 1: AIM-120C-5
Starting Load 2
Fired 2
Missed 0
Hit 2
Event AIM-120C-5 released at 05:49:25 hit Su-25 - destroyed
Event AIM-120C-5 released at 05:49:34 hit Su-25 - destroyed
LOADOUT 2: AIM-120C-4
Starting Load 2
Fired 2
Missed 1
Hit 1
Event AIM-120C-4 released at 05:48:56 miss
Event AIM-120C-4 released at 05:49:14 hit Su-25 - destroyed
LOADOUT 3: BSU-50
Starting Load 2
Fired 2
Missed 0
Hit 2
Event BSU-50 released at 05:59:00 hit Hangar - damaged
Event BSU-50 released at 06:01:43 hit Hangar - destroyed
LOADOUT 4: GBU-24/B
Starting Load 2
Fired 2
Missed 0
Hit 2
Event GBU-24/B released at 05:41:12 hit Parking Lot - damaged
Event hit Hangar - damaged
LOADOUT 5: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
-------------
PILOT SLOT 3:
Human Player: Tomb
Callsign: Tomb
Pilot status - OK
Aircraft status - OK
AA Kills 2
AG Kills 1
AS Kills 2
AN Kills 0
Shoot At 2
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 0
Missed 0
Hit 0
LOADOUT 1: Aim-132 ASRAAM
Starting Load 1
Fired 0
Missed 0
Hit 0
LOADOUT 2: AIM-120C-4
Starting Load 4
Fired 2
Missed 0
Hit 2
Event AIM-120C-4 released at 05:57:22 hit Su-25 - destroyed
Event AIM-120C-4 released at 06:13:33 hit H-6 - destroyed
LOADOUT 3: BSU-50
Starting Load 1
Fired 1
Missed 0
Hit 1
Event BSU-50 released at 05:49:32 hit Hangar - destroyed
LOADOUT 4: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
LOADOUT 5: AGM-65G
Starting Load 1
Fired 1
Missed 0
Hit 1
Event AGM-65G released at 05:40:21 hit ZU-23 - destroyed
LOADOUT 6: AGM-88C
Starting Load 1
Fired 1
Missed 0
Hit 1
Event AGM-88C released at 05:33:22 hit Radar - destroyed
-------------
PILOT SLOT 4:
Human Player: Theron
Callsign: Theron_185th
Pilot status - MIA
Aircraft status - DESTROYED
AA Kills 0
AG Kills 0
AS Kills 1
AN Kills 0
Shoot At 0
Other Player Kills 0
WEAPON DATA
LOADOUT 0: 20mm M61
Starting Load 510
Fired 1
Missed 1
Hit 0
Event 20mm M61 fired at 05:54:02 miss
LOADOUT 1: AIM-120C-5
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 2: Python-4
Starting Load 1
Fired 0
Missed 0
Hit 0
LOADOUT 3: GBU-22/B
Starting Load 2
Fired 1
Missed 0
Hit 1
Event GBU-22/B released at 05:41:00 hit Taxiway - damaged
LOADOUT 4: Mk-84
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 5: 300 Gal Tank
Starting Load 1
Fired 0
Missed 0
Hit 0
LOADOUT 6: AGM-65D
Starting Load 2
Fired 0
Missed 0
Hit 0
LOADOUT 7: AIM-120C-4
Starting Load 1
Fired 0
Missed 0
Hit 0
SnakeBite |
|
|
|
tiag
1417 Posts
Status: offline |
Posted - 01 Mar 2010 : 20:41:26
|
Snake, you are mixing up two things: Experience of the flight leads does not have to do with the kind of TE "endings" that I meant. Yesterday is exactly a conterexample to your argument: almost all flight leads had a lot of experience and the mission ended the way it ended. Unless, in your opinion, you meant that the most flight leads (Griffin, BB, Sabre, myself and Crowebar/Blade) lack the skills to lead flights in AF?!
The kind of TE "ending" I meant can happen in any TE which is not carefully written, in my opinion. Imagine you are attacking an enemy AB over and over. Do you really think that the enemy would not scramble some fighters to put an end on your attack? This is what I meant! I would try to make a strong fighter sweep coming to stop the attack, as I already wrote. That is how things would "likely" happen in most situations, you may agree.
In respect to the TE testing, sometimes just trying offline does not give the results as online. The best thing you can do is to test it online with someone else and see if there are any issues.
Snake, take it as a suggestion of someone who did not like the TE yesterday due to the mentioned reasons. Everyone know that I like everything as real as possible. If I could I would fly just FoF with war planning. Since it is not possible at the moment, I think we could at least fly a little bit more efficiently and realistic in our Sunday TEs. I think I have the right to express my opinion in a polite way as I did.
Cheers
Tiag
 |
|
|
|
Griffin
UNITED KINGDOM
5051 Posts
Status: offline |
Posted - 01 Mar 2010 : 20:59:11
|
While I understand where you're coming from Tiag, I have to say that in real life strike flights would not have gone back to targets for multiple attempts. It would, and should, be one (perhaps two at a stretch) passes over the target and then away to safety.
The constraints of our SOPs in an attempt to limit the strain on processors and bandwidth, will usually make the writer hold back on the number of units defending our targets. There is also the added factor that we want to have some chance of succeeding on the mission and thus defences tend to be restrained. In hindsight I agree that an enforced 'off target' time would have helped the flow last night and that's just down to experience, nothing more. It's certainly something I haven't considered in the past but will do in the future when writing TE's.
I agree that the end of the TE last night was very spread from flight to flight, with plenty of pilots leaving TS rather than enduring the long wait for the strike flight to come home. That is no slur on the strike flight as they were trying to achieve their mission. However, I'm sure ALL the TE writers would have learnt from this.
That said I would like to applaude Snakebite in taking the time to prepare these TE's. Granted the first hit technical issues and we've had a nice debate on the last, but they still take a considerable effort to prepare the 'big' TE's. So thanks again Snake.
|
|
|
|
SnakeBite
USA
1732 Posts
Status: offline |
Posted - 01 Mar 2010 : 23:47:02
|
I'm not criticizing any particular flight lead as I didn't mention anyone. We all make mistakes, but do we all learn from our mistakes?
But ultimately, FL's are responsible for the overall picture of the whole mission. If a FL doesn't respond to calls, doesn't update the picture for his flight members, doesn't direct them as instructed by AWACS or Package commander, or failed to achieve any other important factor, then he failed as a FL.
When a FL figures out he is too close to a "hot spot" then a decision should be made, pushing further into a fur-ball is not a wise move. That's just one example.
Realism: If you need to fly as much realistically as possible, then chances are too minimal to launch one missile on Sunday nights on one month span. And I'm not too excited about that. That may not be exactly true, but it's way boring in real life than it is here in AF.
Here is how the mission was supposed to go:
Intercept flight takes off at 0512 ignoring the two flights of Su-25 that attacked the EWR site. Proceeding to the hold point to engage another raid of Su-25 and Mig-29's. Intercept flight were not supposed to get near the ships.
Intercept flight ultimate goal is to secure our airbase, and NOT to get anywhere near TGT area. This way, Intercept flight gives room for OCA and SEAD Escort.
Ater SEAD flight pushes in, 4xSu-27 launches to shoot down OCA Strike flight, At this point OCA strike and SEAD Escort should engage those contacts. Remember that Su27s took off from Mifol and were flying at 2000ft, meaning you can have a perfect shot on them. And they would be a dead duck for you.
Once the Su-27s are destroyed, OCA flights to proceed to TGT area and take out their targets, we had 8x F-16 loaded with A-G munitions, that's a lot of firepower to destroy all targets in one pass.
Once the OCA strike egresses, Intercept flights again are to engage two different groups, one coming from the NE and one from the SE. Once those targets are destroyed everyone is cleared to RTB.
SEAD Escort flight should have taken out 1x SA-3 , 1x SA-6 and the other SA-3 which wasn't a big factor.
Furthermore, the TE has been tested online with no issues. Any other tips on that?
I see all the issues we had yesterday were human related errors apart from the ground units scattered around.
Finally, I appreciate the fact that you are sharing your thoughts.
SnakeBite |
|
|
| |
Topic |
|
|
|
| 185th VFS |
© 2000-2018 185th VFS |
|
|
|
Sunday 28 February - An Apology
