So about that rain...my first EPQ failure. This makes three consecutive frak-ups. I'm not superstitious, but three is a number. I deem this as an end to screw ups!

I went to RSU but they didn't have enough headsets. It did give me good understanding of what they face. I managed to listen to 10 minutes of radio so even a little is helpful.

Over the weekend, flightmate will stop by to help me with ATC. I'll fly FSX and he will give vectors. This should assist me with that issue.

In squadron, I talked to few folks and everyone is supportive. It seems everyone thinks I will do fine. So far I have 23 sorties, almost 30 hours and 122 landings...I've done it many times over, I know how to do it and just need to show my ability on 89 ride.

Here are pictures from RSU...


Dude going touch-n-go

Usually folks tend to land at "captain bars" which is next to RSU. This guy is landing a bit long...

Observer and Upgrade observer is checking landing aircraft making sure no one lands with gear up.

Tomorrow, relaxing day. Sunday is study.

btw, thanks for support and suggestions. It really does help.

You just do it. You know you can, and you have a whole lot of people who know you can.

What 20mm said.


Wheels

One piece of advice I forgot to mention.

You talked about writing down headings and altitudes. Personally, I would not recommend that. For things that you can't keep in your head or can't be easily set via the instruments, writing down is not a bad plan (ATIS, initial climbouts, ATC route clearances, channel changes with just one radio, etc). However, things that require only one or two numbers, such as a altitude and/or a heading clearance , should probably be left to memory and/or set via a 'bug'.

The main reason is that every iterative step that you put in that process increases the chance of a misinterpretation or error. For stuff that's complicated, sure...it makes sense, writing it down helps keep your mind clear for other things. However, for something simple, you are actually increasing your workload by writing it down.

Just throwing that out there...good luck.

FC

FastCargo. For 87 I wrote first initial directions and following that I used short term memory.

Overall 87 went average. I got most Es with few Gs. It's too late now to debrief. 89 tomorrow....

Good luck today!!!!

Can someone explain what the numbers for the rides mean? 88, 87, 89??? its all latin to me.

89 passed. A mountain got removed from my shoulders. This was the most stressful event in my life! Tomorrow I probably will come into flight room with gray hair.


Ripper,
88 (single time deal) check-ride if midphase failed.
87 - Additional training sortie
89 - elimination check.

Academics test tomorrow. Followed by sim and then night flying.

Congrats, Sim! That's great news!

Sim.


Wheels

Sim, congrats on passing your 89! Press on and keep chairflying...

For someone who was asking what the numbers mean...they are shorthand for the type of ride.

Every simulator or flight has an unique 5 digit alphanumeric identifier...across all SUPT aircraft (T-6A, T-1A, T-38C). As an example, the C5101 ride represents the first contact ride in the T-38C. The letter is the type of ride...Basic (B), Contact (C), Formation (F), etc, etc. The first 2 numbers represent the 'block' of training. For instance, in the T-38C, you'll have:

C51XX - Initial Contact
C52XX - Pre-solo Contact
C5301 - Initial Solo
C54XX - Advanced Contact
C5590 - Checkride

There are a fixed number of rides in each block per the syllabus.

The last 2 digits represent the specific ride number in that block. Obviously, pretty self explanatory...with the exception of the rides Sim has been having.

For instance, if someone had a progress check in the C54XX block, it always has a 88 suffix (C5488). Same thing with practice rides (87), Elimination Check (89), and normal syllabus checkrides (90).

Most folks in the know simply use the shorthand version.

FC