Jump to content

LeVince

Members
  • Posts

    98
  • Joined

  • Last visited

Posts posted by LeVince

  1. It was an idea to help him in his case.According to the the BOC and BOT définitions « CAS aircraft are not required to be TALLY / CONTACT / CAPTURE the target when conducting BOC attacks ». If it was a BOC control, he just have to drop his bomb on the coords, no need to search for the spot, and no need to activate laser.

     

    You’re right by the way, all steps of the CAS process are important, CAS brief and game plan too!

  2. It also depend on the type of control. Is it a bomb on target or a bomb on coordinate control ?

    On a BOT the pilot lase for his bomb, the JTAC uses the laser like any other mean to help you quickly spot the target.

    In a BOC the JTAC will lase for the bomb.

  3. @HAWG63, that is a perfect example.

     

    I like that type of examples because it is not simple. It is a difficult scenario (yes you might have to go over it a few times to understand it) that is close to what you will be doing in practice. most of the scenarios that you see in training videos are very simple and just repeat what the AI JTAC in DCS does.

     

    what will even be more informative is if you would explain the situation and what the JTAC wants to do before hand, so that the viewer has an idea of what to expect and is not taken by surprise by the events.

     

    Example

     

    1). prior to the radio comms, you explain that there is JTAC on ground at this position.

    2). explain that the JTAC is going to use positions A and B if he is contacted by an aircraft.

    eg. if only one aircraft shows up, JTAC will give holding point A, 2 JTAC will give A and B, 3 ... etc

    3). show the two flights approaching and give info (spd, hdg, alt), and then explain that in the radio transmission, flight HAWG will identify itself with the following line, break up the line and show how it will be different to DUDE.

     

    basically i'd like to see each line in a comprehensive radio interaction analysed and explained with a shit load of different examples to show how that line can change according to the situation.

     

    on another note, i know i am asking too much (and i know beggars cannot be choosers) but i see potential in this series

     

     

    Awsome, I agree with you that much more information could be given in these videos, but these videos would last for hours. There are as many possibilities as scenarios and Hawg could write a book.

    I think that given the density of the subject, several small videos such as Hawg publish for now, are better than a long and potentially boring video.

     

    I invite you to watch the "Joint Publication 3-09.3 Close air support" referred to in the first video. You will find a source of inspiration and intelligence, there are many examples of communications and explanations of each step of the CAS. Hawg's videos illustrate some chapters very well

     

    Finally, a little practice, the CAS is dynamic, there is a lot of improvisation. Impossible to go around all the possibilities in video.

  4. La partie gestion dans l'éditeur de mission serait un plus aussi

     

    Qu’est-ce tu veux dire par là ? Si ça répond à ta question pour permettre à une personne de « jouer » JTAC il suffit de placer un véhicule de cocher “player can drive” et d’ajouter un slot “ground commander”.

  5. I find these videos excellent. They are neither too short, nor too long, they summarize by concrete examples the control or routing procedures without entering into explanations that could be very long and boring ...

     

    For my part, I am quite familiar with these procedures and I see these videos as a great addition to the "J-Fire" and "Joint Publication 3-09.3 Close air support".

     

    Besides Flagrum I invite you to consult these two documents that are easy to find on the net, all diagrams in the video are explained in detail and all the steps of the 9-line too.

     

    Vivement les autres!

×
×
  • Create New...