Have created mission point via CDU - now what?

[GunSlingerAUS]

Hey folks

 

I've learnt most of the basics, so now it's time to do the things that the training missions sadly don't yet teach - JTAC operations. I've been flying a user created mission where you need to input the JTAC waypoint via the CDU scratchpad.

 

I've got up to the point where it's inputted, renamed, and I've switched over to mission instead of flight plan. Now what?

 

I can see the new markpoint hovering in mid-air (I'd prefer it to be at ground level, but playing around with its altitude didn't seem to help), but I can't see it on my TAD, so I can't hook it and slave sensors to it.

 

I've attached a trk file showing exactly where I get stuck in this process - any guidance would be greatly appreciated.

cduinput.trk

[GunSlingerAUS]

Hey folks

 

Anybody care to help this little old gunslinger?

[Lange_666]

I've learnt most of the basics...

 

:doh: WOW man, where to start?

 

My jaw hit my desk more then a few times watching your track and after a while it even stayed there... on my desk... i was just unable to put it back up. And then you didn't take off yet.

 

I won't make a list of what or were it went wrong (because i reach my retirement age before i'm done) but what a hectic rush to get your A-10 airborne in the first place (it's there that it goes wrong already). Isn't it better to set it for runway take-off immediately so that at least your A-10 is (automatically) propherly setup before you leave the ground and then continue your learning process?

I may sound a bit harsh but if this was pilot school, the instructor would kick you out with the biggest boot he (or she) could find.

Edited August 8, 2011 by Lange_666

[Wolf Rider]

Couldn't get your track to run...

re-downloaded and it runs

 

 

the grid reference received seems to be for chart 38T and you seem to be set for 37T (the distance of 99, is the give-away)

 

use the CDU on the right side panel, its less cumbersome than the repeater on the flight panel (front dash)

Edited August 8, 2011 by Wolf Rider

[GunSlingerAUS]

:doh: WOW man, where to start?

 

My jaw hit my desk more then a few times watching your track and after a while it even stayed there... on my desk... i was just unable to put it back up. And then you didn't take off yet.

 

I won't make a list of what or were it went wrong (because i reach my retirement age before i'm done) but what a hectic rush to get your A-10 airborne in the first place (it's there that it goes wrong already). Isn't it better to set it for runway take-off immediately so that at least your A-10 is (automatically) propherly setup before you leave the ground and then continue your learning process?

I may sound a bit harsh but if this was pilot school, the instructor would kick you out with the biggest boot he (or she) could find.

 

I didn't think it was that bad, apart from forgetting to turn off the APU until I got to the runway :smartass:

 

Seriously though, all systems were fired up without damage, and everything was in working order, right? How would that procedure have affected the next stage of finding a target after plugging in the CDU co-ordinates?

 

Which brings me back to my original question - what did I do wrong after inputting the CDU data? Wolf Rider, I'm not sure what you mean by your feedback - should I redo the entire thing but just use the CDU side panel? Once I've done that, will I see a new markpoint on my TAD?

 

p.s. Just to keep Lange_666 happy, I'll record another track following the standard start up procedure.

[Wolf Rider]

Have a look at the readout at the screen you would use to input the JTAC coordinates... at the upper left you'll see the reference to 38T or 37T. this may need to be set to the correct for the area you're being sent to by JTAC...The map area is split between two charts (spheroids?)?

This can be modified by the same method as inputting the coords by punching it into the scratchpad and then pressing the button beside the line.

using the UFC/ MFCD or CDU is up to the individual (I suppose)... I find the CDU less cumbersome for JTAC coords... just park the plane into a Path, put the head down and punch it all in, then go for talk on

 

 

pge 459 (1.1.0.9) manual gives some detail

 

and this thread => http://forums.eagle.ru/showthread.php?t=76875&highlight=38T may help as well

Edited August 8, 2011 by Wolf Rider

[159th_Viper]

I didn't think it was that bad, apart from forgetting to turn off the APU until I got to the runway :smartass:

 

Bad enough to lead to your problems :D

 

OK - all that aside, before you put hand to throttle, check your Caution Light Panel. It's there for a reason. Had you done so, you would have noticed the folowing:

 

1 - Ejection seat not armed: Wife/Mistress is not going to be too happy..........

 

2 - GCAS: LASTE failure detected.

 

3 - EAC: Enhanced Attitude Control switch deactivated/failed.

 

 

You need to start-up in accordance with the check-lists provided in an orderly fashion which will ensure that these mistakes do not creep in and ruin your flight. In this instance a major contributor to your issue was a failure to attend to adequate EGI alignment. Again - caution light panel is your friend: Do not ignore.

 

 

Seriously though, all systems were fired up without damage, and everything was in working order, right?

 

Nope - see above.

 

 

How would that procedure have affected the next stage of finding a target after plugging in the CDU co-ordinates?

 

Well, for one, the plane had no clue where it was (EGI alignment abort) so it stands to reason that it would be a guess at best/horribly wrong when it comes to plotting a co-ordinate later.

 

 

 

Which brings me back to my original question - what did I do wrong after inputting the CDU data? Wolf Rider

 

You did not toggle the steerpoint dial to Flight Plan. You entered a new waypoint to your Flight-Plan (named BQQM). With the waypoint so entered, use the UFC steerpoint rocker switch to set the waypoint as your current steerpoint (see attached HUD pic) and then slave your sensors to SPI (steerpoint is SPI as confirmed in bottom left of HUD: SPI generator = steerpoint/STPT).

 

 

 

 

Waypoint as entered by yourself is visible on the TAD - it's just in a Land Far, Far away approx 385nm distant courtesy of an earlier wonky EGI alignment (see attached TAD pic).

 

 

 

 

Pics as above taken from your track - hope this helps. Use the check-lists :)

[Lange_666]

Just to keep Lange_666 happy, I'll record another track following the standard start up procedure.

 

Fair enough...:smilewink:

 

Flippin' a switch here and there a bit earlier then the standard procedure will not cause to much of throuble. But forgetting stuff will cause problems.

Do it right and you will avoid making the problems 159th_Viper listed just above.

Patience is your friend and the EGI has to be aligned before you even move a cm.

 

Like i said, if you want to do it quick, just enter the plane when it's ready sitting on the runway (or even in the air). It's a quicker way to get into training and you are asured of a propherly setup A-10.

 

 

PS: I had quite some fun watching that track...

Edited August 8, 2011 by Lange_666

[Wolf Rider]

and you didn't place a tank in the middle of a highway did you, Gunslinger?

CDU_Input adjusted.trk

[GunSlingerAUS]

Thank you so much for the comprehensive feedback guys - will re-run the mission tonight and upload another, slightly less hilarious, track for your approval

[GunSlingerAUS]

Hey guys

 

I've redone the mission, and used a startup checklist to ensure I did everything in the right order. Once airborne I inputted the CDU co-ords once again, using the very helpful step by step utm coordinate entry powerpoint available on these forums... and once again my new mission point was 380 miles away. I reinputted it again to make sure I had the right co-ords, and it was exactly the same.

 

I've attached a new track, and would love to see where I'm going wrong - I followed the start up and CDU guides to the letter, yet it's still not working.

cdu.trk

[Tholozor]

Make sure the waypoint is in the correct spheroid. i.e. 38T vs 37T

[GunSlingerAUS]

Have a look at the readout at the screen you would use to input the JTAC coordinates... at the upper left you'll see the reference to 38T or 37T. this may need to be set to the correct for the area you're being sent to by JTAC...The map area is split between two charts (spheroids?)?

 

Hmmm, I can't see any reference to 38T or 37T on this screen. Note that the instructions say to hit func 3 on UFC to get to waypoint mode, then I'm selecting waypoint from right MFD = the following screen is where I'm entering the CDU.

Edited August 10, 2011 by GunSlingerAUS

[Harzach]

Hmmm, I can't see any reference to 38T or 37T on this screen. Note that the instructions say to hit func 3 on UFC to get to waypoint mode, then I'm selecting waypoint from right MFD = the following screen is where I'm entering the CDU.

 

Pic stolen from Google images:

 

 

OBS17 displays your spheroid info.

[Wolf Rider]

have a look at the track I put up for you...

 

its basically your original track, in which I "took control" just after you made your attempt with inputting the coords and re-saved as a track.

 

if it runs as saved, you should the 37T/ 38T reference change, and then TGP to target and zoom in

[Dejjvid]

Just punch in 37T (or 38T), hit OSB17 then input UTM coords as you did previously.

 

If u need further assistance, I'll be online tonight (GMT +1), just send me a PM and we can hook up.

[GunSlingerAUS]

Wolf Rider, you're a legend! I'll check that track this weekend, thanks so much for taking the time to help out.

[WildBillKelsoe]

Hey folks

 

I've learnt most of the basics, so now it's time to do the things that the training missions sadly don't yet teach - JTAC operations. I've been flying a user created mission where you need to input the JTAC waypoint via the CDU scratchpad.

 

I've got up to the point where it's inputted, renamed, and I've switched over to mission instead of flight plan. Now what?

 

I can see the new markpoint hovering in mid-air (I'd prefer it to be at ground level, but playing around with its altitude didn't seem to help), but I can't see it on my TAD, so I can't hook it and slave sensors to it.

 

I've attached a trk file showing exactly where I get stuck in this process - any guidance would be greatly appreciated.

 

use this method:

 

1- Prior to takeoff, set Page to WPT

2- Press -->WAYPOINT (LSK L2) on CDU

now you should have the waypoint entry mode.

3- Press the LSK R3 next to (number)? for example 6? to copy this new waypoint to the database

 

Contact JTAC after the above and put the aircraft to autopilot before speaking to JTAC

4- Input JTAC MSL altitude by scratchpad then LSK L2 (one next to height in feet)

5- Input Coords using UTM (preferably) or L/L by scratchpad and LSK L3 for UTM or L3/L4 for Lat / Long respectively, taking note that long coordinates need a zero before them. consult the MSG Recv page for L/L coords or have the JTAC repeat brief for UTM if you missed it.

6- Finally, input the name (JTAC1 for example)for the new waypoint and press LSK R1 (WP Name)

 

7- Switch Page to other

8- Press FPM FSK under the CDU display

now you have the current flight plan

9- Press LSK R1/2/3/4 depending on current active plan highlighted by ** and <--

 

10- Scroll down using rocker PgUp/Dn on CDU panel

11- next to <Next> type JTAC1 on scratchpad and press the LSK next to Next (type first then LSK)

12- look to the HUD and use the selec rocker to the left (next to bezel) and toggle current plan waypoints untill you find the JTAC1 stpt with TTG, Dis, and MH (magnetic heading)

 

13- use the DTS rocker (first or second to the right which if you press should alter altitude to target in 10 feet increments, set to JTACs instruction and press ENT

 

now you should have the target steerpoint as on the ground and ready to attack.

 

I'll post a track to help you here>>

Edited August 12, 2011 by WildBillKelsoe