| T O P I C R E V I E W |
| Griffin |
Posted - 29 Jul 2019 : 16:54:52
Brief for Package 1413
Puma3 is a 4-ship Escort & Redtail2 is a 4-ship AI flight.
Mission - As the first day draws to a close, the 185th has been tasked once again with destroying a battalion of Chinese tanks heading south from Wonsan. The last mission by Plasma1 and Warhawk1 did some damage to the battalion and suppressed the local SAM threats, but there are still seventeen T-80 battle tanks remaining in the group. These must be targeted and destroyed.
The enemy recognise that we are targeting this valuable asset and will be sending extra air cover to protect it until it reaches it's destination.
Friendlies - AWACS and AAR to SE of AO. New AWACs on station south of AO. Carrier group with F/A-18 operating off East coast.
Threats - SA-3 and an SA-10 to NE which should be no factor. SA-5 to the NW, also no factor. AAA likely as well as SA-14 at target. MiG-21, MiG-23, MiG-29A and MiG-31 can be expected around the FLOT area.
Mission Success is given for no aircraft losses and an average of three ground kills per AI aircraft.
Partial Success is given for 1 x aircraft loss and an average of one ground kills per AI aircraft.
IDM will be hosted by Puma3 with Redtail2 as backup host.
Timings
Flight Task TO TOT IDM VHF TACAN FL
Redtail2 AI 2200 2224 11-14 15 11/74 200
Puma3 ESCORT 2158 2220 21-24 16 12/75 260
Comms
Choongwon
ATIS - 135.600
U2 Ground - 275.900
U3 Tower - 230.150
U4 Departure/Arrival - 306.700
U6 Tactical Eyeball1 - 390.700
Alt (Kimpo)
U10 Approach - 363.800
U11 Tower - 240.900
U12 Ground - 236.700
U13 AAR Caddy1 - 369.900 TCN 29Y (set 29Y to receive)
U15 AAR Texaco2 - 251.075 TCN 63Y (set 63Y to receive)
SPINS
Flight paths and weapons are free. Time on Target is critical.
Results
Flight Leads in this Sunday's official mission, "Doggy Bag" are requested to post a debrief of their flight's actions, including any lessons learned or that should be learned by others.
Please put the following information at the top of your post:
Flight Role: (SEAD, ESCORT, STRIKE, Etc..)
Callsign11: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign12: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign13: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign14: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
MS/PS/MF |
| 2 L A T E S T R E P L I E S (Newest First) |
| Noodle |
Posted - 05 Aug 2019 : 09:09:21
Flight Role: AI
Redtail21: "Noodle" AA=1 AG=0 RTB
Redtail22: "Mango" AA=0 AG=0 RTB
Redtail23: "Sabre" AA=0 AG=0 Aborted
MF
Plan
Engage ground targets, focusing on T80, with CBU-97 on a clockwise wagon wheel pattern.
Execution
Same IVC issues as Puma3, sorted but eventually created confusion and comms congestion on VHF, could not send Redtail24 home.
Arrived on target once cleared by Puma3, Redtail22 was the first one cleared hot as Redtail21 was turning cold as Puma3 was still busy clearing the target area.
All Redtail flight experienced blue text and Sabre got kicked out, leaving us with 2 AIs (which I think later created a little traffic conflict over the homeplate as we could not send them home).
We set our CCRP profile to a burst altitude of 2000ft for our CBUs, Redtail21 and 22 came off dry on first pass. On second pass, Redtail21 released 4 CBUs, had visual on the explosion but no secondary explosions to be seen. At that point not much was heard from Redtail22, nothing to be heard on UHF from Puma3 and Redtail21 got a nail 23 on RWR. I quickly turned hot, positive ID bandit on M4 IFF and fired 2 slammers before turning cold.
I then re-joined with Redtail22 who still had one pass to go.
Communication as very bad at this point, nothing to be heard on UHF, or VHF (except AI) so we decided to use TS for intra flight and Sabre would relay the info to Puma3.
We called it off soon after and RTB.
Expected 16L but ended up being 34R. Clear weather, straight in approach, recovered as planned.
All in all with VHF confusion from the beginning, AI congesting the frequency, blue text, etc… The flight could have been worse. CBU profile needs testing during the week, will post on ATO for a KOTAR run on Tuesday.
|
| Vosene |
Posted - 04 Aug 2019 : 21:10:53
Flight Role: ESCORT
Puma31: "Vosene" AA=3 AG=0 KIA
Puma32: "Reds" AA=1 AG=0 RTB
Puma33: "Griffin" AA=1 AG=0 RTB FF
MF
Plan
Setup NW-SE CAP while AI engaged ground targets
Execution
Strange issue with IVC comms on take-off delayed departure. Once resolved Puma3 quickly got airborne.
Entered CAP area 5 minutes ahead of schedule and immediately picked up 2-ship MiG-29A. 1&2 engaged with Slammer each and splashed both. Called AI onto target and went back onto CAP.
During this time had several large blue text freezes and then lost IVC. In sorting this out picked up 2x Mig-21 inbound from West. 1 engaged both targets due to 2 being out of position. Both Migs splashed but 2 also engaged with a Slammer went bandit was already hit due to lack of comms at that time.
3 then had lead for a MiG-23 engagement. Fired two missiles at one target, splashed. The other MiG-23 was splashed by the AI flight. In the getting back onto CAP 3 fired at 1 by mistake. 1 was in a turn and low on airspeed and, unable to avoid the missile, was shot down.
3 and 4 came off CAP and RTB for an approach onto R34.
Learning Points
Issues with IVC comms then blue text pauses and lost IVC. need to investigate.
Shootdown was exacerbated by loss of IVC and issues with IFF but should still have been avoid using D/L position. 1 tried to call BuddySpike but did so on IVC initially, by the time he corrected and called it on TS due to the loss of IVC the missile was already in the air.
Overall, given the issues experienced and loss of comms between flights, the mission went surprisingly well apart from the Friendly Fire incident, which came during a period of high workload exacerbated by the comms issues.
 |
|
|
