Enroute Class pass rate

Please share any insight for us
Your leads should go over what’s important but get every point possible leading into radar is one you’ll hear a lot, which is true, my class had someone pass with a 70.54 so points can save you. For radar: there’s not really a secret formula for success. You show up and run the problems, ask questions on stuff you don’t understand and try not to make the same mistakes over again. If you can understand the radar scope and what situations require what solutions you’ll be fine and should be able to pass.
 
Your leads should go over what’s important but get every point possible leading into radar is one you’ll hear a lot, which is true, my class had someone pass with a 70.54 so points can save you. For radar: there’s not really a secret formula for success. You show up and run the problems, ask questions on stuff you don’t understand and try not to make the same mistakes over again. If you can understand the radar scope and what situations require what solutions you’ll be fine and should be able to pass.
You don’t even need to come up with solutions. The d siding at the lab is literally just doing administrative tasks
 
Please share any insight for us
If you miss a point out or manual handoff or anything, don't just shrug it off and forget about it, do the point out or the action you missed. They might deduct points for that error, they might look over smaller things, tbay happened to me on one eval. The evaluator had two grade sheets. One was official and one was everything on it. A too late manual printout, but I did it anyway taking the 16 point error, saved me from 30 points of bullshit errors. This was just for that evaluator but finish even though you got the error.
 
If you miss a point out or manual handoff or anything, don't just shrug it off and forget about it, do the point out or the action you missed. They might deduct points for that error, they might look over smaller things, tbay happened to me on one eval. The evaluator had two grade sheets. One was official and one was everything on it. A too late manual printout, but I did it anyway taking the 16 point error, saved me from 30 points of bullshit errors. This was just for that evaluator but finish even though you got the error.
I would agree with this. Some of the evaluators do want you to pass and running a good problem overall and showing the evaluators that you understand what’s going even if it’s late may earn you some points back. I definitely had situations in all 3 of my evals where the evaluators went a little easier on me because of that. Not every evaluator will do that, but it’s very possible.
 
You don’t even need to come up with solutions. The d siding at the lab is literally just doing administrative tasks
Your leads should go over what’s important but get every point possible leading into radar is one you’ll hear a lot, which is true, my class had someone pass with a 70.54 so points can save you. For radar: there’s not really a secret formula for success. You show up and run the problems, ask questions on stuff you don’t understand and try not to make the same mistakes over again. If you can understand the radar scope and what situations require what solutions you’ll be fine and should be able to pass.

I mean you still have to solve red and potential yellow alerts by altitude or routes, not all of which work. Same with departures. So that’s probably 50%+ of your workload. Your R-Side is basically blind when it comes to planes coming together though. Overall the course is extremely do able though, no real gotcha’s. I would say for the most part people probably over study while they are there.
 
I had one of the evaluators that are known to be tough on my first run and I APREQ’ed a climb with JAN approach 2 miles outside their boundary (has to be done before they get within 2.5 miles of their boundary) and my evaluator moved my hand from the vector line tool so he could display the 2.5 mile boundary markers and obviously took the 16 points off for it. My second evaluator gave me my points back for a late point out ??‍♀️ Always do everything even if it’s late, because you never know what type of evaluator you have
 
I had one of the evaluators that are known to be tough on my first run and I APREQ’ed a climb with JAN approach 2 miles outside their boundary (has to be done before they get within 2.5 miles of their boundary) and my evaluator moved my hand from the vector line tool so he could display the 2.5 mile boundary markers and obviously took the 16 points off for it. My second evaluator gave me my points back for a late point out ??‍♀️ Always do everything even if it’s late, because you never know what type of evaluator you have
Did the first evaluator’s name rhyme with Fuck?
 
I mean you still have to solve red and potential yellow alerts by altitude or routes, not all of which work. Same with departures. So that’s probably 50%+ of your workload. Your R-Side is basically blind when it comes to planes coming together though. Overall the course is extremely do able though, no real gotcha’s. I would say for the most part people probably over study while they are there.
Dude eram tells you if the solution works you aren’t actually looking for conflicts on the scope
 
Back
Top Bottom