If the second TUG of BW did not exist and the file with one base of Cv was shot away, then the Cv would make a charge move that would pass the the TUG of BW that shot at them and finish contacting nothing at the adjusted move distance for the charge move (assuming the direction of charge was straight forward)?

If the charge had resulted in C1 contacting B4 then C1 would fight B4 as a frontal contact in the charge phase, but what happens in the melee phase? Does A3 fight B3  &  C1, with C2 in support, fight B4 (all as frontal contacts)?

When a file is destroyed in the charge phase and bases press forward, as allowed under Pg85 7.4, is any new contact with enemy bases treated as:
1.  a new charge... ie combat is fought in charge phase with charge phase claims
or
2.  a continuation of fighting to be fought in combat phase... giving contacted bases chance to turn post charge phase using cards

QuoteIf you meet the conditions for a flank charge  then you can wheel (at the start of the charge) into the flank.  If you don't meet the conditions of a flank charge but still contact the flank it is treated as a frontal charge

An enemy is contacted in the flank by a charge but the charge does not count as a flank charge....  so the impact is fought as if a frontal charge, but what happens in the following melee phase(s).... do files that would normally qualify as 'behind the flank' get the flank bonus?

QuoteSuspect you are not using the Compendium edition of the rules as in that 9.5 G is casualty removal in combat.

I am using page 146 of the Compendium edition which is 9.5 I Supporting Files in Combat, specifically 3.4 which says "Or be in such a position that aligning would have resulted in the above situations" - the "above situations" are the requirements to be a supporting file.

You are right, I'm using the old "poor man's" edition!
But even so, the BGs can't align, so the files can't be supporting files.

QuoteSlightly complicated. The front base of the file is an engaged base being able to be a supporting file and, therefore, cannot be moved with an M1 move - other bases that do not count as engaged could move.

Hi Nik,
Is the following not true:
The left hand files (as you look at the pic) of both BGs are not in contact with the enemy and are too distant to permit alignment... therefore are not supporting files... therefore are not engaged and can be moved by M1 moves
I refer again to Rule 9.5G 1.1.1 thru 1.1.3

This is an odd one, but I don't think the suggested ruling is consistent with the qualification for being a supporting file – Rule 9.5G... Part 1.
Surely, it's a 2 vs 2 combat with no supporting file for either side? Neither side can align files into a position to qualify as a supporting file as defined in paras 1.1.1 thru 1.1.3. However, for either side, spending a card on an MF1 move would allow a legal supporting file to be created.   
... sorted?