Login to Account Create an Account
[LN]Desert Raider from my perspective
Posted 28 April 2013 - 09:35 PM
Performance of the OCB guys was top notch as was that of our guests, thank you all. From Bravo squad I was really really impressed with the level of team work and the way we seamlessly worked together. You guys were fantastic, your drills were excellent and you were all really switched on.
In relation to the heli crash that can not be placed on the pilot. Without access to external view a pilot MUST have a full crew as they provide the eyes for the pilot who has limited field of view. Sure the comms broke down a little but that wasn't the major contributor.
I personally loved the mission and really enjoyed it, many thanks Lyndiman for a top notch job. Just needs Headless Client.
- Levelcap, ren111 and Redlock Holmes like this
Posted 28 April 2013 - 11:25 PM
Key things I noted:
- Training and the lack of aviation applying SOP. (This is probably root of the disaster)
- It was great to have so many airframes up at once.
- JTAC role could have been run better (As mentioned previously SOP & training is what it boils down to) - Faster TOT (Time on target) & use of assets.
- Lag was also a key problem which should be looked at. Whilst flying CAS on the AH-6 I came across lots of desync which made it look like I was going to crash.
Posted 29 April 2013 - 08:07 AM
Deconflicting the airspace is an important job. When orbiting a LZ and providing cover do a 'wheel' around - this way you can see the lz at all times. Also, when lifting off announce it like good VFR procedure. Just say '*callsign* lifting' If youre not flying in formation then you should expect a minimum of 1000 ft separation. If two callsigns are orbiting they wheel in opposite directions at different altitudes to provide overwatch from different angles.
I think we should have run 2 choppers with a loader for each.
Still good fun tho!
It seems some people's positions were stolen when they disconnected which I didn't know about till the end. Will kick people if this happens again.
Posted 29 April 2013 - 09:14 AM
Posted 29 April 2013 - 11:14 AM
Posted 29 April 2013 - 11:25 AM
Lyndi, for the next mission Foxtrot-2 was coming into position at 2229 to the North of the AO.
Also, I like the idea of using the X-Ray platforms as overwatch / fire support. Gives the chopper pilots a challenge (and two more sets of eyes) and develops crew co-operation which is something we need to work on. I am a very big fan of having 4 man X-rays, Pilot, Co-Pilot (FFIR Operator), Crew Chief, Door Gunner. It's just a matter of using a chopper that has the FFIR or gimbal camera that can be used to suppliment recon observations, BDA's etc.
For the recon squad/s a 117 or similar would have also been handy since we were in position at the start / constantly moving forward to the next AO prior to the main contingent. Even if it's mounted in the vehicle it would help to keep us in contact regardless of where we are.
Finally from me, Foxtrot-2 did a fantastic job and maintained good discipline despite never firing a shot. Hopefully Lyndi will change that for us next run.
P.S. More enemies next time.
- Tromac likes this
Posted 29 April 2013 - 08:56 PM
Complicating things without crew chief is clearing above from conflicts and keeping sight of other aircraft in what are awful visual conditions. Having said that communication can alleviate this. Simple calls such Lyndi suggest along with a couple of others would help.
I cannot emphasize the below statement enough.
Losing sight of your lead is a sin. Not telling him you have gone "blind" is a cardinal sin and a recipe for disaster.
Where are the SOPs for Air?
Posted 30 April 2013 - 10:35 AM
- ren111 likes this
Posted 30 April 2013 - 01:23 PM
- Tromac likes this
Posted 30 April 2013 - 03:32 PM
Posted 30 April 2013 - 04:28 PM
after looking at lyndi's vid. maybe squad leader calls to pilot that the squad is out and is clear to take off, when it is safe to do so.
The problem with that is the squad leader needs to focus on what he's running out into as well as his own troops. We need to operate with full aircrews when possible and when not possible with external views. This also occurred because the pilot was being talked onto the LZ rather than given the opportunity to choose a spot and communicate that to the other aircraft, comms were tied up completely with the talk on which meant the pilot couldn't let the others know what was happening.
Posted 30 April 2013 - 07:00 PM
Posted 17 May 2013 - 06:47 PM
in regards to this, being the JTAC on that night, having a JTAC operate in depth from the rear of the combat is totally inefficient, relying on sections to give accurate co-ords for a JTAC, then waiting to get those co-ords, relayed via 1 - 3 people then coordinating an attack solution, giving that to the pilots awaiting a read back and then finally receiving rounds onto target is a HUGE time delay, if you want to think about a fix for this, the answer is far simpler than overlaying training program from start to finish. PUT the JTAC as an imbed up front so they can see the calls.... OR ..... Imbed the JTAC with your Recon/Over watch Element. so that in turn, they can see the enemy and call the CAS elements into target, thus ending in a much faster TOT, sure you guys may have seen a slower turn around time from the ground, but when you are relying on a radio only and no eye ball of enemy movement, you simply wont get the TOT from call to bombs dropping as you had hoped for. From here out with the SOP's, if you want a JTAC in a TAC then give them the best possible position to make his calls to the flight lead.
Key things I noted:
JTAC role could have been run better (As mentioned previously SOP & training is what it boils down to) - Faster TOT (Time on target) & use of assets.
Edited by ren111, 17 May 2013 - 06:49 PM.