Monday, June 11, 2007

Pad Management 101

With all the modern technology available to air traffic controllers, it often surprises people that one of the most powerful tools at their disposal is a simple notepad and a simple pen. A good controller can lose his radar, his traffic management tools, and just about everything else that's plugged in and still work traffic so long as he's got:
  • His eyeballs
  • His memory
  • A working radio
  • A pen and notepad
The purpose of this notepad is to keep track of essential information regarding your traffic. Every controller has a different system for doing it, and there is simply no wrong way or right way to do it. However, some ways are definitely better than others. As you progress through the training and get broken in on the labs, you'll start to realize what the better methods are.

For instance, let's say Cessna 889PT calls in 7nm south with information Juliet, requesting full stop. I reply and tell him to enter left base, Runway 28L. He enters the pattern, and I clear him to land. Afterwards, he turns off and I switch him to ground.

When I first started, I was writing something like:

C172 | 889PT | 28L | J | 7S √

Makes sense, right? He's an arriving (↓) Cessna 172, call sign 889PT, he's going into Runway 28L, he's called in ATIS Juliet, he's 7 miles south, and he's been cleared to land (√). All important information, right?

WRONG. That's a ton of extraneous information and a ton of writing. Your eyes need to be outside the windows, not inside staring at paper. The more you're scribbling, the less you're controlling.

The system I'm using now was given to me by an instructor on Friday morning. We were talking in the Tower3D lab and I mentioned that I was trying to nail a process down, and he went ahead and passed on his "tribal knowledge" that had been taught to him by a controller 30 years ago.

The principle is this: You divide your pad up into two columns, one for the runway closest to you, and one for the runway furthest to you. You then list the aircraft under whichever runway you've assigned them to. What you write on the pad is minimalist. You do not use the pad to sequence, you do not use it to control. It is just there as a reminder for critical information that you need.

So here, let's break down our runways and replay the scenario:





28R
28L


9PT

That's it! Three digits/letters in the correct column is all you need. Everything else is irrelevant, or can easily be drawn from memory.
  • You don't need any arrival ↓ marker since it's obvious by the fact that A) you should remember talking to him and B) any departures would have their own strip handed to you by the Ground controller.
  • You don't need his ATIS code; you just need to confirm he has it on initial call up.
  • You've told him to enter the pattern for 28L, so you don't need his location since you'll know where he'll be coming in.
  • You don't need the first two letters of his name, unless there's another aircraft in the pattern with a similar call sign.
  • As for his aircraft type, you don't need to put it down so long as you can remember it as "CESSNA 9PT" or "CITATION 2BZ" However, if you get busy or need something to jog your memory, you can always use an abbreviation for it, such as "72 9PT" (with "72" being short for "C172"). Other examples include:
    • 28 = P28A = Piper Cherokee
    • 35 or BZ = BE35 = Beech Bonanza
    • 77 = C177 = Cessna Cardinal
    • 31 = C310 = Twin Cessna 310
    • 58 = BE58 = Beechcraft Baron
    • 60 = BE60 = Beechcraft Duke
    • KA = BE90 or BE20 = King Air or Super King Air
    • BJ = Beechjet
Ok, so this system works great for the two parallels and for "full stop" aircraft. But what about Runway 34? What about after they've landed? What about Touch and Goes? Well, let's tackle those.

Runway 34/16: If an aircraft calls in and we put him straight in to 34 or 16, we need to think about where the first conflict lies. For instance, if you clear a guy into 34, the first intersecting runway he'll hit will be Runway 28L. If we put him into 16, it'll be Runway 28R. That dictates under which of the two columns he'll go.

So, let's say we have another aircraft (Cherokee 288PM) arriving from the south and he requests 34. We do this:






28R
28L


72 9PT

28 8PM (34)

We put him down just like 9PT, but now we add 34 to the right and circle it. Now we know that he's coming in to 34, and we need to make sure that 28L is clear first, followed by 28R. As you can see, it's still minimalist. Pure, essential information, placed in the right spot.

Ok, so 9Pt touches down and turns off the runway. 8PM follows right after, coming in on 34. You switch both aircraft to Ground. How do you indicate that they've successfully landed and are now on Ground frequency?






28R
28L


72 9PT

28 8PM (34)


Just line them out! They're done, bam, gone, out of your hair. You can effectively forget about them once you push them over Ground.

But then, Cessna 424KB calls 7 miles east, inbound for 3 touch and goes and a full stop. You clear him to touch and go, using 28L as well. How do we format this?







28R
28L


72 9PT

28 8PM (34)

( 72 4KB )

  • You circle 4KB's callsign, indicating that he's doing touch and goes (you know, running laps around your runway). That way you can look at your pad and instantly tell who your T&G-ers are.
  • He indicated that he wants 3 touch and goes. What you're going to do is, as you clear him for each T&G, you're going to draw a "\" slash below his callsign. Once he touches down, powers up, and lifts off again, you'll draw a "/" over that slash to make it an "X". This indicates that the loop has been closed and that you'll need to clear him for his next T&G.
So, let's say he's already done one touch and go, and you've cleared him for his second. Your pad should look like:







28R
28L


72 9PT

28 8PM (34)

( 72 4KB )
X /

So, good ol' Cessna 4KB is done for today and wants to land. You clear him to land, he touches down, you switch him to Ground, and you're done with him. At that point, your pad should look like:







28R
28L


72 9PT

28 8PM (34)

( 72 4KB )
X X X

All aircraft have been landed and cleared from your frequency.

And that's it for today! As you can see, it's important to use symbols and shortcuts to keep things clean and organized. However, the most powerful tool of all is simply your own brain and your short term memory.

Sunday, June 10, 2007

Weekend 4: Shooting and Studying

First off, I'm sorry for not posting a lot about the tabletops. I will get to it this weekend. There's just been a lot to absorb and it's been a rollercoaster ride.

Saturday:


Kelly and I went shooting again today. Stress relief! I really feel my accuracy is improving. Hell, the first shot of the day was a bullseye! (It all went downhill after that, LOL...)

I got to shoot Kelly's .45 caliber Springfield 1911 too. Man, that thing is comfortable. It's a round twice as big as the Makarov's, but the recoil felt half as much. I guess that's what you get when you compare a $165 military sidearm (my Mak) against a $700+ piece of mechanical art.

Me shooting my Makarov:

Kelly laying waste to her target:

"Eyes and ears" are so stylish...

Sunday:

We've got the CTO test (Control Tower Operator Certification Exam) coming up Thursday, so it's time to hit the books. Joanna and Kelly came over today for a while. Matt O. was supposed to show but never did.

The CTO exam study guide is pretty intense. It covers a lot of things that we never explicitly covered in the academic portion of our training. In fact, a lot of it comes out of the Federal Aviation Regulations (FAR) and the Airmen's Information Manual (AIM) used by pilots. As a pilot, some of it was review, but for someone who's never taken the FAA written exam I would highly recommend cracking open FAR's or taking a look at the AIM. If you've had at least the private ground school, you should have a leg up on things.

Common things that are covered in there include:
  • Emergencies and bomb threats
  • Air space restrictions and types
  • Instrument procedures and approaches
  • Loss of radio contact
  • Administrative stuff like facility ratings and eligibility
  • Aircraft categories
  • Wake turbulence
After Joanna showed up, we moved back inside and did a bunch of runs on the paper airport. We had a good time with it, getting our phraseology down and coming across unanswered questions to bring up with our instructors. It was a lot of fun, since we were more or less goofing around with it.

Saturday, June 09, 2007

Days 15 - 18: Tabletop Madness

I can't think of any way to describe the Tabletop experience other than a roller coaster ride.

The ascent: The academics are your foundation, showing you what the tools are. You know the labs are coming, so you try to absorb as much as possible. The days to the labs countdown and you're eager to get going, while still apprehensive about putting all of this information into action.

The big drop: The track drops away from your feet and you feel yourself falling helplessly. Your first day or so in tabletops will be the hardest. You will feel like you're being shotgunned with all kinds of feedback from the many different instructors. You will be told to do things 18 different ways by 18 different people, and some will tell you in a nice way, and others will irritate the hell out of you.

...and now back up: Whee! We're in a loop now, and we're feeling the wind on our face. The fear is gone and now we're enjoying the ride. Things are clicking now. You're making your wake turbulence calls. You're issuing traffic. You've had a one or two go-arounds and one or two "cancel takeoff clearance!" moments, but so far you're feeling good.

That's where I'm at now. The first few days were rough. However, on my last two tabletop runs I feel like I nailed it. I had two of the strictest, cockiest instructors on each of those runs, and they were pleased with my performance.

Several things continue to be a little bothersome, like wake turbulence advisories (not the actual 2 minute wait, but the advisories for landing aircraft of any wake turbulence issues) as well as the "Idiot Stick". I've gotten much better with the latter, but sometimes I get busy and forget to get or give that stick back so the runway's operational again.




For those who haven't gotten to the academy or who are still in Academics, here are some observations I've made about what to do/not do:
  • DO SOMETHING: If you see a situation developing, act! Tell someone to go around, extend downwind, etc. Take action and take control. You're in training to be a controller, not a spectator. The lab instructors hate it when you just sit there and watch things come apart. Analyze, decide, and ACT.

  • Justify Your Actions: Be able to explain everything you say and do. Your instructor's not exactly going to be thrilled if you told an airplane to do something "because you felt like it" (even if that's truly the case).

  • Plan Ahead: Don't just focus on what you have in your jurisdiction now. Try and get the picture of what's coming. If you're Local, keep an ear out for what Ground is doing and how many strips they're working with. A lot of those are coming your way. If you're Ground, keep an eye on how many airplanes are in the pattern, what type they are, and what runway they're going to.

    For instance, if you're on Ground and you see that Local's got got a Delta 757 who just called over the Final Approach Fix, a Cessna 172 landing on Runway 34, and a Bonanza who was doing touch and goes that just called for a full-stop, that's three airplanes you're going to be talking to very shortly. Try and get Local (if they're not too busy) to talk with them and see where they're parking. Just from the aircraft types, you've got at least one figured out: the Delta's going to the terminal. The other two will be going to either Falcon / Spartan FBO's or to the Main Ramp, so keep in mind if they're going to the main ramp you'll have to coordinate a crossing. If they're going to the FBO's, then life's easy - "TAXI TO SPARTAN AVIATION VIA GOLF" or "TAXI TO SPARTAN AVIATION VIA HOTEL". Bang, done.

    In other words, think ahead and keep your options open.

  • Be Patient: Not only with yourself, but with your classmates. If you're trying to get an airplane off the runway at Taxiway Delta, and your ground controller puts someone nose-to-nose with them for an intersection departure, don't get mad. You're both learning.

    Use it as as lesson for:
    1. Resolving a situation quickly and effectively.
    2. Learning how to better coordinate. For instance, after that, you can tell your ground "If there are anymore intersection departures, put them out through Charlie so they don't nose-to-nose."

  • Learn to Bite Your Tongue: Some of the instructors are very nice and very positive. I look forward to working with them. Others... they want you to do things their way, say things their way, and ONLY their way - no matter what anyone has told you. Just humor them.

  • Pad Management: The sooner you learn to manage your notepad, the better. I assure you that you will get 15 different ways of managing your pad. Find one that works for you, and keep it as simple as possible. I'll write more on this later.

  • Make Idle Chatter: I don't mean tell your life story and distract yourself from the traffic. However, chatting with your instructor during a lull in the traffic can help you relax and clear your head.

Wednesday, June 06, 2007

Day 14: Warm Up

Today's Lessons:
  • Block Test #5
  • Comprehensive PV Written Exam
  • Tabletop Orientation
Today we finished the last tiny bit of the academics. Block Test #5 was as standard as the others - no surprises there. The Comprehensive PV, however, was 100 questions long and covered everything we've learned from Day One. I did well with an 88 on it. The highest score I heard was a 91, and there were a few that were lower, down into the 70's. It's a lot of material, and a lot of the questions dealt with stuff that is not operational in nature (i.e. stuff that just needs to be memorized rather than material that can be "worked out" via common sense).

Then, we moved on to tabletop orientation. It was a rough start, but we worked through some problems and got a feel for how best to flow with it. We did get our scheduling, so we can see how much time we're going to be getting on each position.

Here's basically how the scheduling works: There are two tabletop labs, Room 124 and Room 163. We also have two stations of Tower3D setup in our classroom. Every day there are 7 "runs" - a.k.a. run-throughs of individual problems, which usually last around 40 minutes. For each run, you are assigned one of the following positions:

FD = Flight Data (Both Tabletop and Tower3D)
GC = Ground Control (Both Tabletop and Tower3D)
LC = Local Control (Both Tabletop and Tower3D)
FLC = Floor Local Control (Tabletop only. You hold the little planes up around the table and make airplaney sounds.)
FGC = Floor Ground Control (Tabletop only. You taxi the little planes on the surface of the table and also make airplaney sounds.)

There is a number preceding each position that lets you know what room or station you will be working in. An example of a daily schedule of 7 runs:
124GC | 124FLC | 163FLC | 2FD | 124FGC | 1LC | 163FLC

If the preceding number is 124 or 163, you're in one of the aforementioned tabletop labs. If it's a single digit, you work that position at a specific station in the Tower3D lab. It's pretty straightforward, and they try to make it so that everyone gets an equal amount of chances. Nonetheless, you should contrast and compare with others to make sure that everyone's on the same page.

Monday, June 04, 2007

Weekend 3: Saturday and Sunday

Saturday: Native American Festival

I'd been looking forward to this for a while. I'm very much into exploring and learning about different cultures and their different aspects - music, art, food, etc. This was a pretty unique experience, I must say. It wasn't very organized, but it was interesting nonetheless, seeing and hearing bits of the Native American culture.

Here's the video I cut from it:




Sunday: Nothing much.

Quiet day at home. Studied for the tests tomorrow, both the Written PV and the Block V test.

Weekend 3: Friday

Man, I had a pretty active weekend this time around.

Friday Night: Burger Time

A bunch of us had made plans to hit the Oklahoma Redhawks Minor League baseball game tonight. Kind of a class deal. I really felt like getting out of the house and checking out something new and different, so this hit the spot. Plus, at $6 a ticket, you can't beat the price! The weather was pretty crap, so only 7 of us made it out there: Me, Blake, Emily, Matt, Stacy, Joe, and Raul.

While we were standing around by our seats, waiting for the game to start, this guy comes up to us and asks for four volunteers to be part of the inter-inning entertainment. Turns out he wants us for a McDonalds "Build a Burger" contest. Basically, you split into two teams of two, put on hamburger bun suits, one person lays down on either 1st base or 3rd base, and the other person proceeds to pile a bunch of foam "ingredients" on them. Emily and Stacy said yes pretty quickly. I said "screw it" and signed up, and was then joined by Matt, making it a 2 vs. 2 girls vs. guys thing.

At the middle of the 3rd inning, we met the guy up by the concession stand and he led us down into the bowels of the stadium. We ended up just inside the Redhawks' dugout, which was pretty cool. The guy proceeds to give us the "strategy" for this ridiculousness. Matt and I concur that, since he's tall as hell and can run fast, he'll be the "runner" and I'll be the one who goes out and lays out on the plate.

Attack of the Burger People:
So, we all put on our bun suits, don our "mentally challenged" crash helmets, and head out on to the field. Emily and Stacy head out to 3rd Base while Matt and I rush over to the 1st Base. We put on our bun suits with a quickness, and just as we finished putting them on, we hear the announcer going "Go!!!!". Matt and I look at each other, look at Emily and Stacy (who are hauling ass to 3rd base), and we bolt to the 1st base. I flop down, Matt piles all the ingredients on, and swan dives on top. Freaking ridiculous. It couldn't have taken more than 10 seconds.

Blake shot a funny-as-hell video of it from the stands, which I posted on YouTube:



After that stupidity, we stayed at the game for maybe a 1/2 hour more and then headed out to this club called Citywalk. I got over the "club thing" years ago (I spent a good part of my formative years on South Beach, either going to clubs or playing at them in various bands) but this place was pretty cool. It had a lot of different rooms, playing a lot of different kinds of music. And for those who aim to get hammered, they had nickel beers in the bottle, with the first one free after you pay the $10 cover.

We had a hankering to play some pool and the tables upstairs were taken, so we moved into the piano bar downstairs. It had one empty table, so we racked up and started shooting away. And man, do I need practice. The good thing was that, well, most of us sucked. The only one who knew what he was doing was Joe. All I can say is that I hope we can all vector airplanes to their destinations better than we can smack billiard balls into pockets.

Joe the Pro:
Definitely a cool night. It was good to hang out with some different people and do things out of my regular comfort zone (and if dressing up as a hamburger in front of thousands of people is in your comfort zone, please seek help...).


Sunday, June 03, 2007

Day 13: Headsets!

Today's Lessons:
  • Visual Operations
  • IFR Arrivals and Departures
  • Tabletop Orientation
We finally finished academics today. Everyone is relieved and eager to get going in the labs.

As a bonus, we also received our headsets. I'm definitely starting to feel that "controller vibe" now. I've seen all of the previous classes walking around with their headsets slung around their necks. Now it's our turn.

The last two academic lessons were pretty straightforward. IFR Arrivals and Departures covered both radar and non-radar techniques for arrivals and departures. There's a lot of "busywork" involved with the IFR's, including getting a release prior to takeoff and delivering rolling reports for each departure. Also, in a radar environment with successive departures, you need to fire them off with at least 15 degrees of divergence to provide separation. For the nonradar portion, it's good to brush up on the 1 minute / 2 minute / 3 mile rules that govern how you space your departures out.

Visual Operations focused on using visual techniques in an IFR environment. Visual approaches, visual separation, contact approaches, special VFR, VFR-on-top, etc. Each has their own specific requirements as far as weather goes, and all still need to take into account aircraft performance, route of flight and wake turbulence.

Visual Separation is kind of an inside joke with controllers it seems, and a very powerful tool at the same time. By telling an IFR aircraft about another aircraft and telling him to "MAINTAIN VISUAL SEPARATION" you're taking the separation duties largely out of your hands and putting it in the hands of the pilot. He can fly circles around the other aircraft, and it's not really your problem. When your Conflict Alert's screaming bloody murder and your supervisor walks over with a "WTF is going on?" look on his face, you can just throw up your hands and say "I had visual!"

Today's Note: Someone made a comment that the headsets they gave us are a little cheap-feeling. They're not as far as I'm concerned - they're very lightweight and unobtrusive. I looked the model up on the Plantronics site. This is the one I (and most of the other people in the class) selected: http://www.plantronics.com/north_america/en_US/products/cat1200043/cat380046/prod440084 As you can see, it's over $130.00. They also offered us an over-the-ear one but I thought this might be more comfortable over long periods. Also, I think the in-ear design makes for better clarity.

Day 12: Home Stretch!

Today's Lessons
  • VFR Depatures (Continued)
  • Runway Incursions
There's an energy in the classroom now. We're getting close to the end of academics, and people are anxious to be done with the "book learnin'" stuff. I know I am.

There's been a lot of information shotgunned at us over the past couple weeks. It's really concentrated, and we really do need the breaks every 45 minutes to an hour so we can stand up and clear our heads. After a while, it becomes hard to stay awake and keep absorbing. I estimate that, for the 8.5 hours we're there every day, around 2-3 hours of that is spent on break or lunch. At first I thought it was excessive (yeah, yeah - how can someone have too many breaks?) but as the days wore on it got tougher to keep sharp and fresh.

Day 11: Feeling Positive

Today's Lessons
  • Block Test IV
  • VFR Arrivals
  • VFR Departures
If there's one way to sum up today's lessons, it would be "positive control".

Here's an example: Cessna 172PT calls in from the Spartan Aviation FBO. Now, you could tell him "CESSNA 172PT, TAXI TO RUNWAY 28R" and just leave it at that. However, that opens up a can of worms, since he could get to 28R from a million different directions. He could go via taxiways Golf-Bravo-Alpha... or Hotel-Juliet-India-Charlie-Bravo-Alpha... or.... you get the idea. And when you've got landing traffic or traffic coming out of the terminal, there's a very good possibility you could wind up nose-to-nose. On top of that, that clearance was a straight "taxi to runway XX" clearance, meaning he can cross anything along the way - including active runway 16. Big no-no.

Instead, use positive control. You're the controller. You are in control. So, you know...control!
"CESSNA 172PT, RUNWAY 28R AT CHARLIE, TAXI VIA GOLF, BRAVO. HOLD SHORT RUNWAY 16".

It's a longer transmission, but it leaves no question for either you or the pilot as to where that aircraft should be going. He's going to head via Golf, turn left at Bravo, and hold short of Runway 16. Once he gets clearance to cross, he will proceed to Charlie, turn right, and hold short of Runway 28R for an intersection takeoff. It leaves out any mystery, and allows you to plan ahead.

Practical Exercises

We did some scenarios today on the board, which allowed us to explore different options for getting traffic in and out of our airport.

I think one of the strongest things you can develop is a sense of timing based on aircraft speed and performance. To be successful in this job, you need to have a good understanding of what each airplane's performance envelope is and what kind of speed they will be flying at during different phases of flight. This will help you anticipate more and gauge how much time you have to get an airplane in or out.

Here's an example:
You've got: 1) A Baron holding short of 28L who just called ready for takeoff, 2) a Cherokee N8PM abeam the numbers on downwind for 28L, and 3) another Cherokee N8DS that just called in 6 miles east, inbound straight-in for 28L as well.

Ok, for starters, both Cherokees are slow-movers. The one on downwind is probably making around 80-90 knots, and the one 6 miles out is probably at 90-100 knots. Let's round them to 90, which gives us a distance-per-minute of 1.5NM. The Baron, as a twin, is signifigantly faster.

At 1.5NM per minute and 6 miles away, Cherokee N8DS will take 4 minutes to reach the airport, so he's barely even a factor unless we really screw something up. So we back-burner him for now and turn our attention back to Cherokee N8PM on downwind and our twin-engine friend, the Baron. Cherokee 8PM has to fly 1 mile past the runway threshold to intersect the base leg. Then he has the base leg itself, which is another mile. Then the final leg - 3 miles total. That gives us 2 minutes.

Armed with those 2 minutes, we go "BARON 123, ACADEMY TOWER, TRAFFIC CHEROKEE ON DOWNWIND, RUNWAY 28L, CLEARED FOR TAKE OFF." Out the gate goes the Baron - he's wheels up and gone. Since we're oh-so-confident in how many minutes we have, before the Baron even begins rolling we can call N8PM: "CHEROKEE 8PM, ACADEMY TOWER, TRAFFIC, DEPARTING BARON RUNWAY 28L, RUNWAY 28L, CLEARED TO LAND."

At the point when 8PM is turning final, 8DS should be at least 2 minutes behind him. At this point, you can go ahead and clear him to land. "CHEROKEE 8DS, ACADEMY TOWER, NUMBER TWO BEHIND CHEROKEE ON FINAL FOR RUNWAY 28L, RUNWAY 28L, CLEARED TO LAND."

Voila! Problem solved. When 8PM comes in over the threshold, he'll have a whole 3 miles between him and the Cherokee behind him. This meets the 3000 foot Cat I separation 6-fold. And, we didn't have to delay the Baron at all.

Wednesday, May 30, 2007

Aviation Stories

Two funny stories today from our instructor:

Braniff 727

He was working in Oklahoma City tower at a time when Braniff International Airways was still in operation (the airline folded in 1982). During that period, Braniff had a promotion called "Braniff Bucks". If your Braniff flight was late, you would be paid a dollar for every minute over the scheduled arrival time. 20 minutes late, you'd pocket $20. Naturally, this gave the flight crews a real incentive to get to their destination as quickly as possible.

Well, one day there's a Braniff 727 inbound to Will Rogers Airport in Oklahoma City. They're cutting it close on the clock, and from the direction they're coming they'll have to take a full pattern to approach the runway into the wind. So, to save time, the pilot requests a straight-in opposite-direction landing, meaning he'll be landing with the wind at his back. This isn't explicitly dangerous, as long as the wind isn't too strong and the runway is long enough. The reported wind isn't too high, so the tower approves the request and clears him to land.

So in he goes. The tailwind is higher than reported and, to compound the situation, his approach speed is over what it should be. He touches down, realizes that the speed's way too hot, and proceeds to basically stand on the brakes. As he's gripping the yoke, he depresses the mic toggle, and now everyone on the frequency can hear the mayhem in the cockpit. The pilot is swearing up a storm, and in the background you could hear the flight engineer counting down the Runway Distance Remaining markers. "Three thousand! Two thousand! One thousand!" Somewhere along the way, the landing gear collapses, and the Boeing does a slip-and-slide right off the end of the runway and takes out the approach lights.

As it grinds to a halt, the pilot releases the mic and the frequency goes silent. Everyone on board is relieved and glad to be alive. The captain and crew are dreading what this will do to their careers.

Without missing a beat, the local controller keys his mic: "Well..." he says dryly,"at least you beat the clock!"



IFR F-16

The airport where our instructor was working was under serious IFR conditions. They had an F-16 trying to land through the soup, but after two failed attempts he was running low on fuel. He only had enough for one more try, and specifically requested that the tower put their best guy on the radio to talk him down. If he didn't make it this time, he'd take it straight out and eject.

So the tower puts their most experienced guy on the radio, the guy who's been controlling since the only thing in the air were pterodactyls. He talks that F-16 out of the sky, bringing him right into the pocket. The fighter touches down beautifully, rolls out on the runway, and flames out before he can turn off. It was a lucky day for the pilot. The trucks roll out to the airplane and retrieve the pilot.

Later on, the hotshot controller hangs up his headset for the night and leaves for home. Due to that airport's layout, he needs to cross the runway and movement areas to get out. So he hops in his car, heads on to the foggy dark runway... and proceeds to drive into the F-16. That's right, the same multi-million dollar fighter that he talked down earlier was still sitting on the runway, in the dark and muck. And now it has thousands of dollars of damage due to the same guy who saved it from destruction!

Tuesday, May 29, 2007

Day 10: Caution, Wake Turbulence

Today's Lessons:
  • Block Test III
  • Wake Turbulence
  • VFR Arrivals

We had Block Test III today, which covered lessons 14-18 (up through ground control). I got 2 wrong and walked away with a 94%.

Afterwards came a brutally dry session of Wake Turbulence lessons and practical examples. The best way I've found to describe Wake Turbulence is as a logic puzzle. It's a seemingly endless combination of "If A = B then B = C... but does C = A?" puzzles that just become a little mind-numbing. There's a lot of factors to take into account, from aircraft size to the departure point on the runway.

The problem is that, as dry as it is, it is absolutely vital to successfully passing this course. You will be making a ton of "HOLD FOR WAKE TURBULENCE" and "CAUTION WAKE TURBULENCE" calls throughout your training. You need to know it well enough that it will just roll off your tongue without a thought, because when you're getting busy you can't stop and think about anything.

However, I think I've broken it down to its essence. The packet we were being taught from was pretty lengthy and it went into a lot of unnecessary detail and repetition. I like things simple, and I think I managed to simplify it enough to put it into a few basic rules.

To start, there's three common factors for each Wake Turbulence rule:
  • Holding time
  • Can it be waived?
  • Is it measured from when the aircraft begins its takeoff roll, or from when it rotates and leaves ground?
And from there, we go on:

3 Minute Holds (Non-waiverable / Timed from Aircraft Rotation):
  • Anything at an intersection behind a Heavy/Boeing 757.
  • All departures in the opposite direction of a departing Heavy/Boeing 757.

    Simplified: If you're taking off behind a Heavy/B757 from anywhere other than the Heavy's end of the runway, you're getting 3 minutes.


3 Minute Holds (Waiverable / Timed from Aircraft Rotation):
  • Small behind a Large or Small behind a Small-Plus at an intersection - same or opposite direction.
  • Small departure from opposite direction behind Large departure or Large low/missed approach.

    Simplified: If you're taking off after a Small or Large from anywhere other than the other aircraft's end of the runway, you're getting 3 minutes... but you can waive it.

2 Minute Holds (Non-waiverable / Timed from start of Takeoff Roll):
  • Anything (Small, Large, Heavy) behind a Heavy/Boeing 757 that's departing from the same runway end the Heavy started its takeoff roll from.
  • Parallel runway departures where the flight path of a departing aircraft will take it through the flight path of a Heavy/Boeing 757 departing ahead of it from the parallel runway.
  • Departure from intersecting runways following a Heavy/Boeing 757 if the Heavy's runway intersects the departure's runway.

    Simplified: If you're taking off after a Heavy, or your path will intersect with a Heavy - either in the air or on the ground - you're getting a non-waiverable 2 minute hold.
Situations that do NOT need Wake Turbulence separation:
These can all be cleared for immediate takeoff.
  • Small behind a Small (duh).
  • Small behind a Small-Plus
  • Small behind a Large
  • Small-Plus behind a Large
  • Large behind a Small
  • Large behind a Small-Plus
  • Large behind a Large
VFR Arrivals

After the Wake Turbulence lectures, we started learning more about the tools needed for maintaining proper VFR separation and managing traffic flow. Examples include "MAKE RIGHT THREE-SIXTY" and "CONTINUE DOWNWIND".

Included in this was the happy-fun of Same Runway Separation. This covered Cat I, II, and III separation minimums, which varied depending on which type of aircraft was landing and/or taking off.

Today's Note: Red Earth Festival is coming this weekend. I'm psyched. I have a thing for native cultures and art, so I'm looking forward to checking out the different exhibitions, music, performances, and what-not. I'll be in class for its first day (Friday the 1st) but I'll definitely be checking it out over this coming weekend.

Weekend Two: Pistols, Pirates, and Idiot Sticks

Fairly busy weekend here.

Saturday

Kelly and I'd made plans to go shooting today. She came by in the early afternoon (after braving 1 hour Walmart lines to get a cleaning kit for her pistol) and we set out to the range. H&H Gun Range is just down the street from me (south of Reno, just east of Meridian) and we set up shop there for a little bit. Kelly brought her .45 out and laid waste to a paper silhouette. I don't think he's going to be having any silhouette kids anytime soon...

It felt good to take the Makarov out again. I hadn't shot it in about a year, so it was like getting reacquainted with an old friend. I won't win any points for bullseyes, but I was happy with the results at 30 feet:

And here's the Mak itself:

The craziest part of the whole deal is that the range only cost $9.50... for the entire day! Back in Miami, Ace's charges $15.00 per hour. Un-freaking-believable.

Afterwards, we grabbed something to eat and came back to my place. The music came on and we just mellowed, cleaning the guns. It was pretty funny, as Kelly's gun has about 25 separate parts... and the Makarov breaks down into two. I was done cleaning my entire gun by the time she was finished with the barrel of hers.

We met up with Matt afterwards in the outdoor park here and studied a bit for the Block test that's coming up on Tuesday morning. It was a beautiful day and it didn't feel right to be cooped up inside.

Afterwards, the three of us headed down to Bricktown to see Pirates of the Caribbean: At World's End. Awesome movie. It was a lot more action-oriented than the previous two. Parts 1 and 2 were much more comedic and focused, while this one kind of careened all over the place. It's a hell of a ride and a good closer to the series, but I think it's the weakest of the three. It had some really amazing action set-pieces (the climactic battle has to be seen to be believed. Just...wow) but overall it's story was weaker and a bit more forced. Also, Jack - who in the first two was a driving force to each film - just kind of takes a back seat to all the action, occasionally chiming in to deliver a one-liner. Keira Knightley still looked smoking hot though... and that made everything ok! :)

Sunday

Got more progress done on the TED Center videos for Cynfyn. I finally got some music tracks down that work with the presentation. Two of the five segments are good to go, and I've been plugging away at #3 and #4. The After Effects animations on this pass look much better than the earlier ones - I'm happy.

Overall I like video, but it can be a real pain in the ass when it wants to be. Like with any long-term project, I'll be glad to see its conclusion.

Monday

We had our first at-home set of runs today. Matt, Paul, Kelly, and Joanna came over for a while. We went over a lot of the phraseology, using the callsigns they had provided to us at the academy. It was good to actually say it out loud instead of just reading it. We also practiced stripmarking using the strips I'd printed up. We went over many of the procedures required for taxiing aircraft, working with helicopters, and getting a workable flow of traffic into and around the airport. We weren't very organized, but that was fine. The next session will be even better I think.

One thing we touched on was runway crossing coordination between Local and Ground. At the Academy, Ground has a big ugly yellow metal bar that has "Runway Occupied" written on it. It is used in coordination with Local Control to let them know the runway is occupied. In ATC parlance, this sort of device is called a "memory aid". In the real world, we call it the "Idiot Stick", because it makes you look like a total moron when you forget to use it.

I made my own at-home version, lovingly called the "Dumbass Stick".

Here's how the runway crossing procedure works: Let's say you're Ground, and you want to taxi an aircraft across Runway 16, an active runway, at the taxiway Bravo intersection. Here's how the dialog goes:

You (to Local): "Cross runway one-six at Bravo."
Local: "Cross runway one-six at Bravo."
You hand the Idiot Stick to Local, and he puts it within view on his strip bay. This is to remind him not to land or depart any aircraft on that runway, since it is now occupied.
You (to the aircraft): "Cessna one-seven-two-papa-tango, cross Runway one-six".
Aircraft responds and then taxis across the runway. You observe that the aircraft has completely crossed the runway edge.
You (to Local): "Runway 16, RCC (short for Runway Crossing Complete)"
Local hands you back the Idiot Stick, and runway 16 is back in operation.

It's not overly complicated, but like everything else in ATC, once you start getting busy it gets cumbersome to remember to do it all. Losing coordination and losing the flick will get people killed, and in this business the devil is certainly in the details. However, sometimes the errors are simply so glaringly obvious you have to wonder what the person was thinking.

There was one person who failed her Local PV because of a stupid mistake involving runway crossing coordination. Ground coordinated a crossing of runway 16 with her. Then, just as she finished telling Ground she could cross the airplane, she cleared an airplane to takeoff on the same runway. Bam. Deal.

I think our next at-home runs will be more coordinated. I was talking with Kelly about maybe having a few people on dedicated ground and/or local for a while, instead of switching back and forth every few "planes".

Some quick phraseology snippets of commonly used commands:

Taxiing an aircraft from Spartan Aviation to the intersection of 28R and Charlie, with hold-short instructions at one-six:
"CESSNA 172PT, ACADEMY GROUND, RUNWAY 28R AT CHARLIE, TAXI VIA GOLF, BRAVO. HOLD SHORT RUNWAY 16."

A VFR popup calls in 7 miles east:
"N172PT, ACADEMY TOWER. MAKE STRAIGHT IN RUNWAY TWO EIGHT LEFT."

Calling for IFR release:
"DEPARTURE, TOWER, REQUEST RELEASE FOR AMERICAN 619."

Landing Aircraft on 28L:
"N288DS, TURN RIGHT NEXT TAXIWAY. HOLD SHORT RUNWAY 28R, REMAIN MY FREQUENCY."

Anyways, that's it for today. Pretty good weekend. I wish Mary was here though...

Today's Note:
I started watching Heroes. Wow, interesting show. I really like how it focuses 90% of its energy on the characters (at least so far in episodes 1 - 3). They're realistic people... who just happen to have superpowers. Very different than the typical comic book superhero whose character is actually defined by their abilities.

Friday, May 25, 2007

The Hot Wheels Airport

"Cessna Four-Kilo-Bravo, Academy Tower, runway Two-Eight Right, cleared to land. Traffic, housefly on left base, runway Two-Eight Left."

We got some airports and plastic planes to take home today and practice over the weekend.

I also made myself some laminated strips and got some dry-erase markers. For four markers and six laminated sheets (total 48 strips) it came out to $15 at Office Depot. Not bad for something that's infinitely reusable.

We also got a list of some of the common callsigns we'll be seeing, so we can use them on our stripmarking and get familiar with them.



I'm heading out in a few to go meet some of the class at Cimarron's steakhouse over on Meridian. I'll be back on later to finish the post and catch up on what else we did today...

Day 9: Wind Shear Advisories in Effect

Today's Lessons
  • Ground Movement
  • Wind Shear/LLWAS
  • Local Control
I'm kind of tired today, so I'm not going to into too much detail about these.

Ground Movement was pretty straightfoward. It just covered basic taxi instructions, with an emphasis on getting proper read back. Always keep an ear out in case an aircraft doesn't read back a hold short instruction, or says "28L" instead of "28R". A girl failed her PV because of the latter. Always remember: a stupid mistake like that can get someone killed.

LLWAS covered the different systems and procedures required for handling Low Level Wind Shear. It included the actual hardware, the phraseology for the ATIS (the title of this post), and what the local controller is supposed to do when wind shear is detected.

Lastly... Local Control dealt with coordination procedures, military takeoff procedures, safety alerts, traffic advisories, runway visual range, position and hold, and much more. As you can imagine, Local has a pretty hefty amount of information.

Thursday, May 24, 2007

Day 8: Better Start the Shower...

...things are about to get dirty! We're ramping up towards the move into the labs. The next few days will see us bouncing back and forth from classroom to labs, so everyone's getting excited.

Today's Lessons
  • Block Test #2
  • General Control
  • Position Relief Briefings
  • Ground Control
We started the day off with Block Test #2. I scored a 91% on it. Not bad - I missed three, and one of them was a stupid mistake. Oh well.

General control covered broad subjects like duty priorities, traffic advisories, safety alerts, military operations, and TCAS resolution advisories. It was just a lot of procedural stuff, not really anything specific.

One of the most important things it did cover was the format for reporting traffic alerts. That is absolutely key to success in the Academy airport environment, since you've got two parallel runways with simultaneous aircraft operations.

For instance, let's say you have United 482, a Boeing 767, on a four mile final for 28R and a Beechcraft Baron N30144 turning base for 28L. Your traffic calls would go something like:
  • "UNITED 482, ACADEMY TOWER, RUNWAY TWO-EIGHT RIGHT, CLEARED TO LAND. TRAFFIC, BEECHCRAFT BARON AHEAD AND TO YOUR LEFT, ON BASE FOR RUNWAY TWO-EIGHT LEFT."
  • Then... "BARON ONE-FOUR-FOUR, ACADEMY TOWER, RUNWAY TWO-EIGHT LEFT, CLEARED TO LAND. TRAFFIC, AHEAD AND TO YOUR RIGHT, BOEING 767 ON FOUR MILE FINAL FOR RUNWAY TWO-EIGHT RIGHT."
To put it simply, if there's any chance that two aircraft will become a factor for each other, make the traffic call and make sure they know where they are in relation to each other.

For Position Relief Briefings, we went over the four-step procedure for a controller to relieve another controller. Basically, it's 1) Preview, 2) Verbal Briefing, 3), Assumption of Responsibility and 4) Review the Position. To summarize the entire lesson, do not rush and do not leave anything out. Be clear, concise, patient, and ask/answer questions. Both parties share responsibility, so both need to do it right. There is a checklist for it - USE IT.

Ground Control is looking pretty fun and challenging. Taxi the airplanes, ensure they have the weather, mark the strips with the runway they're heading towards, and - above all else - maintain coordination with Local. That is the whole key to it: coordination. The Academy airport is setup to force you to coordinate, since all of the east/west taxiways cross the diagonal active runway (16/34). I really need to start working hard on the phraseology for it, such as "CROSS RUNWAY 16 AT BRAVO" and "RUNWAY CROSSING COMPLETED". Exciting stuff - at Miami Dade I only worked Local and supervisor, so this will be the first time I touch Ground.

On another note, our instructor kept reporting on another class who was PV-ing. Apparently 5 or 6 out of the 24 failed and had to retake. He said that their instructor was going to come by tomorrow to give us the low-down on what they did wrong.

Plans for the weekend are already in the works. I might go shooting with Kelly, so I picked up a few odds and ends so I can clean the ol' Mak. (It hasn't been cleaned since, wow, last year? Meh, it's Russian. It'll work fine, LOL.) I'm also trying to get a group together to go see the third Pirates of the Caribbean movie.

Today's Note: Man, as much as I hate Walmart, it is quite funny the collection of crap you can walk out of there with. I went in there today to get some odds and ends, and walked out with:
  • New spatula (to replace the one I annihilated a few posts ago)
  • Gun cleaning kit
  • Pistol targets
  • Chicken nuggets
  • Shaun of the Dead DVD
  • Mexican cheese mix
  • Refried beans

Wednesday, May 23, 2007

Day 7: Happy Hour

Today's Lessons
  • FDIO
  • ATIS
  • Clearance Delivery

Right off the bat we continued with FDIO, working on a batch of exercises that showed us how to create, amend, and remove flight plans, along with printing their strips and sending departure messages to other facilities. This was actually pretty cool. I'm kind of techie, so it was neat to learn how FP's are managed in the field. It was pretty easy once you learned the codes (which were easy on their own) and the fields.

The fields were in typical flight plan order.
  • 01 is the command code (i.e. what you want to do to the flight plan). For instance, AM = Amend Flight Plan, SR = Strip Request (print strip), RS = Remove Flight Plan....
  • 02 is the Aircraft ID (N12365, AAL745)
  • 03 is the aircraft type (C172/A, B744/R)
  • ...04 beacon code, 05 speed, 06 departure fix, 07 proposed departure time, etc...
For instance, to change AAL745's type to a Boeing 767-200 and proposed departure time to 1330Z, you would enter:

AM AAL745 03 B767/2 07 P1330

... and BAM. Done. Easy.

This is an old-school FDIO machine:


After we finished the FDIO exercise, it was on to the wonderful world of ATIS (Automated Terminal Information Service). I've heard a million and one ATIS broadcasts during my time as a pilot, so it was (somewhat) interesting to hear how they're made. Overall, the lesson was pretty boring and involved a lot of discussion of antiquated equipment. I did find out some fun facts - for instance, while I had always thought that the ATIS is recorded every hour, it turns out it's recorded whenever there's a weather update or a NOTAM released.

Afterwards, we went down to the tabletop lab and messed around with the equipment there. In that system, there's no actual piece of ATIS gear - it's all a software simulation of the real thing. I tried my hand at it, but for some reason got a little tongue-tied, giving me the kick in the ass I need to work on my annunciation and vocal presence.

Then came Clearance Delivery. We're going to be spending 7 days in the tabletop labs, which is the only lab where we will have an actual C/D position open. The TSS and Tower3D labs have only Ground and Local control positions, so this is really the only place where we will be doing Clearance Delivery before heading to our facilities. You're not specifically graded on Clearance Delivery, but your performance directly impacts the Ground and Local Control positions since your stripmarking and clearance operation needs to be on the money. In short, you do not want to be the one slowing down the show.

As with the two other positions, you have to manage your strips well and have Academy-specific procedures to fulfill. For instance, when you deliver an aircraft's clearance, you have to put a checkmark in block 13 of the strip. And once the aircraft has taken off, you need to send a departure message to Academy Approach letting them know and put a checkmark in block 18 saying you've done so. Aside from that, there's a bunch of duties you need to be taking care of, such as entering/modifying flight plans and managing the ATIS.

After work, I hit the Walnut Gardens Happy Hour with a classmate (after studying for tomorrow's block test of course... :) ). Every Wednesday they throw down a free beer keg-fueled "Happy Hour" for the folks staying at FAA housing places. This time they had nachos instead of the usual pizza up in the back lounge area. The "cheesy meat dip" looked rather mysterious, but ended up being pretty good. Whatever - the price was right.

Today's Note: None... Sleep deprivation sucks. I'm turning in early tonight to catch up on the sleep I've been missing over the past few days. This 5:15am alarm is killing me...

Picking Cacti Out of the Landing Gear

My dad sent me this video today of a harrowing landing in Honduras. Remind me never to visit this place - ever.


Insane Landing In Honduras - Watch more free videos

It put me on a search for some more harrowing landings.

Here's one into Funchal, on the island of Madeira. The airport's runway is partially built on a massive series of pylons extending out into the ocean. It is essentially a giant concrete aircraft carrier, capable of handling most large airliners.

This is a nice combination exterior and cockpit video:
http://www.youtube.com/watch?v=1S4TnxVskKI

But nothing beats Saba. Unofficially the world's shortest runway with scheduled airliner traffic, and officially closed (Winair and any other airlines are required to have a waiver in order to fly into it), it is essentially a strip carved into the side of a Caribbean volcano. 1000 feet long, it is surrounded on three sides by sheer cliffs. Only STOL aircraft can safely use it.

Here are a couple great cockpit videos:
http://www.youtube.com/watch?v=6RU_fk6zNmc
http://www.youtube.com/watch?v=0JP-yvfs-U0&mode=related&search=

Tuesday, May 22, 2007

Day 6: Strips and Spatulas

Today's Lessons:
  • Tower Visibility Test
  • Block Test 1
  • Academy Airspace
  • Strip Marking
  • FDIO
Today we took our first actual tests. First up was the National Weather Service exam for Tower Visibility. 50 questions covering the subjects we learned yesterday, like prevailing visibility, variable visibility, and tower/surface visibility. I ended up with a 94%, which I was very happy with.

Afterwards, we took Block Test 1, which covered mostly things we'd learned last week. I got a 100 on that, mostly on luck since there were a few questions out of the 20 that I wasn't really 100% sure on. Whatever the case, it's a good start to the course.

We then covered the Academy Airport airspace. This actually has a lot of memorization. The material included instrument approach procedures, VFR reporting points (aka landmarks), navaids (VOR, Markers), and - horror of horrors - airways. The airways were a pain - I can only imagine what the En Route guys go through to memorize their area charts.

Stripmarking was cool. I'd never actually done it at Miami Dade, so it was good to learn the symbols and the Academy-specific procedures. Nothing too complicated it seems.

Lastly, we started our FDIO (pronounced Fido, like the dog) lessons. FDIO is Flight Data Input/Output. In short, it's the system that allows you create, modify, delete, and print flight plans and their associated strips. Apparently it's a very common system in towers that interfaces with an ARTCC host computer. The guy who was teaching it was fun and tried to make this very dry material interesting. Part of me was bored to tears, but at the same time I was happy to get my curiosity satisfied as to how flight plans are created.

Today's Note: I have discovered today that plastic melts. Just ask the spatula I used to scrape the burger remains off my brand new grill pan. I guess I've just been used to these quality ones we had back at the house. Whatever the case, the poor spatoola was reduced to:

And my poor formerly spanky-new grillpan has melted plastic all over it.... :(

Day 5: It Ain't Rocket Surgery!

Week two begins...

Today's Lessons:
  • Tower Visibility
  • Airport Conditions, Uses, and Lighting
  • Academy Airport Layout
Today was mostly about Tower Visibility. Tomorrow we have the actual National Weather Service exam for it. This test was one of the Great Mysteries of the courses, simply because no one could really explain it. It requires an 80% to pass, and people have been known to fail it, so quite a few people were worked up over it.

It actually turned out to be pretty straightforward, with a few caveats. What it boils down to is you need calculate the highest visibility for half of the horizon. Let's say to the north you've got 5 miles visibility, 4 miles visibility to the south, and 3 miles to the east and west.

So, let's reason it out:
  • You've got 25% of the horizon at 5 miles, so it doesn't equal half.
  • However, match it up with the 4 miles and that means that at least half of the horizon has 4 miles visibility (25% has 4 and 25% is over 4), so you can claim 4 miles of prevailing visibility.
  • You can forget about the other two sectors which were at 3, since you've already got a prevailing of 4 from the other 50% of horizon.
Bam - prevailing visibility of 4 miles.

It's also got a lot more rules involved. For instance, if 3 of 4 sectors are over VFR minimums, but one is under, then you need to list all of the sectors in the remarks - except for those that match the prevailing visibility. Confused yet? :P

Example: North visibility is 5, East is 7, South is 5, and West is 2. In your METAR weather observation, you would then put:

5SM .... RMK VIS E 7 W 2.

Explanation: West is below 2 miles visibility, so we automatically need to mention the sector visibilities in the remarks. Since North and South equal the prevailing visibility, you can leave them out. However, since East and West differ from the prevailing, you need to include them in your remarks.

We also covered Variable Visibility, which boils down to averaging measurements, and Tower/Surface Visibility. There are rules for them as well, but I won't bore you with the details.

None of it is overly challenging. You just need to pay attention to the rules and apply them.

The lessons afterwards covered the airport layout and airport conditions/usage. The Academy Airport (AAC) is pretty straightforward, with a few bottlenecks and niggles to keep things interesting.

Today's Note: Rocket Surgery! Russ, our lead instructor, was explaining something simple and said "It's not rocket surgery...". I thought it was funny as hell... what's funnier is that I can't remember what the hell he was talking about when he said it. I'll have to use that line somewhere.... :(

Monday, May 21, 2007

Weekend One

Saturday

Today was a pretty quiet and relaxing day. I actually slept in past 9:30am - not surprising considering that for an entire week I'd been getting up at 5:15am.

For lunch, Mary and I hit our favorite Mexican place, On The Border. As always, the food was plentiful and cheap, and we had a really good server.

After dropping the leftovers back at the apartment, we went down to the Bricktown area. Bricktown is essentially the hotspot in OKC, with movie theatres, nice restaurants, clubs, and bars. Not exactly South Beach, but it's got some charm with its busted, battered brick buildings (enough "b's?") and downtown backdrop.

We ended up seeing Shrek the Third. It was pretty amusing, but I've got to agree with a lot of reviewers who've said that they simply tried to throw in too much. They've gathered too many characters over the past two movies, and now feel compelled to bring them all back. The end result is a movie called Shrek where Shrek himself has maybe 1/2 to 1/3 of the screentime and the plot has been reduced to "Get Arthur and come back". It was a better second sequel than Spiderman 3 (which was just a sloppy disaster) but after this I don't really want to see Shrek IV.

Afterwards, we spent the rest of the day back at the apartment hanging out and spending time together. Dinner was a reheat of lunch's leftovers and a healthy dose of popcorn. We watched Anger Management with dinner - my God does Jack Nicholson need a beating in that movie.

Today's Note: Parents, for the love of all that is good and holy, please do NOT bring your 5 month old infant to the movies. The kid can't even say "mama" yet and you're somehow expecting it to miraculously follow plot points and understand dialogue? I understand that kids learn a lot by watching movies and TV, but when your child has not yet learned to control its own neck you might just be jumping the gun. Save us the annoyance and leave your screaming bundle of joy with the sitter.

Sunday


I took Mary off to the airport this morning at around 4:30am. It was a horrible feeling, watching her head out through the security line. I honestly don't even really want to talk about it. The few days apart we've had over the years have been hard enough - but 3 months? I don't really have words for it- I just miss her so terribly...Thankfully she got in safely and her parents picked her up.

I spent the morning hanging around the house. Later on, Kelly from my class came by and we went to the Sooner gun show at the OK City Fair Grounds. She drives this huge red Toyota pickup truck, but handles it like a small car. It was such a shocking change to be in a car with *gasp!* power locks and *shock!* power windows after driving my P.O.S. Cavalier for a week.

Anyways, we picked up some ammo and I got a new case for my Makarov. There was really nothing else - all the good stuff had been sold over the previous couple of days, so all that was left was the dregs. All-in-all it was actually a pretty disappointing show. Afterwards, we headed over to a Chinese buffet place and grabbed some lunch, and she dropped me off back at the apartment.

Mary got on the webcam later on and we talked for a while. At least we're able to see each other. Webcams may be considered old technology now, but there's still something magical about not only hearing your loved one, but being able to see each other. Smile together, laugh together, watch TV together (as always, it's fun to pick apart Rachael Ray), etc. It's not the same as having her here, but.... it's something.

I made my first on-my-own meal tonight: Gnocchi in pink sauce. I made a heck of a mess in the kitchen, but whatever - I had enough for dinner and the following day's lunch. I unfortunately made too much sauce, and even after sopping some of it up with bread I ended up having to toss some. Oh well...

Today's Note: What the hell were a B-47 and B-52 fuselage doing sitting in the middle of a County Fair parking lot? Seriously, no joke. I wish I'd had my camera with me. They looked like crap, lying on the ground with no wings, but they were there. You can see them clearly here.

Here's an old picture, while the B-47 was still intact.
Being Oklahoma, I had expected to see plenty of cars up on concrete blocks... but Cold War jet bombers? Wow.

Wednesday, May 16, 2007

So the Adventure Begins...

Well, started training yesterday in Oklahoma City.

Day 1: Handshakes and Paperwork

It was a long day of paperwork and indoctrination.

The coolest part is that, as of around 11am May 15th, I can say that I am officially both a Federal Employee and an Air Traffic Controller (I'll just leave off the "in training" part for now. :) )


Day 2: Introductions

The first two days have been full lots of administrative stuff that's, well, kind of dry - benefits, life insurance, travel reimbursement, etc.. The best part by far has been meeting new people.

Most of the students are excited and looking forward to getting into the meat of the training. There are, however, a couple students who are very bummed out about being sent to high cost of living areas and are thinking of quitting. One woman was being sent to a Level 7 seasonal terminal in an area where the average home price is in the $ millions. The cheapest place she can find is a $1400/month room in a basement...with no kitchen.

For the Miami Dade folks, I've seen a whole bunch of alumni here for both Terminal and En Route in various stages of training.

Here's a quick list:

* Greg Weinbrum
* David Brookman
* Tuvar Akio
* Michael Shmeisser (sp?)
* Shawna
* Don Ellington
* Shulji (sp?)

There's two more guys that I know by face, but not by name.

Day 3: Tetris With a Career Attached

Today I retook the AT-SAT with my class. It's part of CAMI's research initiative, and only moderately less painful than being hugged by an Iron Maiden. I scored a 91% on, a few points lower than my previous 94% score. Not bad, considering I spent most of the Letter Factory test trying to keep from falling asleep (literally).

For those not in the know, the LF test is similar in concept to Tetris: you have to put the right pieces in the right place. The difference is:
  • The "pieces" in this case are the letters A, B, C and D coming down on four conveyor belts.
  • Each letter is one of three colors, and needs to be placed in a box of the matching color.
  • Only one letter of each time can go in each box.
  • Every once in a while, a letter other than ABCD comes down and you need to push a "Quality Control" button to remove it.
  • When you run out of boxes, you need to order more.
  • After each run-through, the computer asks you a bunch of situational awareness questions. (Ex: What letters would have been needed to fill the boxes you currently had open?)
I remember the first time I took this test, back in Miami. It was like an 8 hour heart attack, plugging through the math, angles, scan test, etc., hoping to come out on the other end with a passing score and a checkmark on my path to ATC.

Day 4: Fun with Weather Products

Today was all about tower equipment and weather products.

Curt, one of our A-leads, gave us a rundown of all the different equipment we'll be using in the tower. Frequency selectors, lighting controls, ILS monitors, wake turbulence timers and other things featured in the lecture. There's a lot of toys up in the tower, and by the time he was done I had a good grasp of how they all worked. Afterwards, we got to go over to the table-top lab and see the different pieces of equipment in person.

Following the Tower Equipment lesson (and lunch) we met our weather instructor, who's a former AFSS-er and doesn't do a very good job of hiding his bitterness towards the FAA over the takeover of Flight Service by Lockheed-Martin. I can't blame him.

The first part of his session involved discussion of numerous weather products. Many of them are familiar from my flying (METARs, TAFs, Area Forecasts, HIWAS) but it was definitely interesting to see the other side of things. I had never given much thought to how these products were generated, but thanks to this class now I know the different requirements for each. It's a lot of info and somewhat tedious, but at the same time it's useful in a "fun fact" sort of way.

The second part of the lesson was a CBI course on the ASOS automated weather reporting system that's used on most airports to determine the weather. Now, I'm big into technology and all that, and it was cool to learn how to generate METARs/SPECIs and transmit them to FSS. The problem was the presentation itself. It was extremely frustrating in that you couldn't skip ahead, and you had to sit there and listen to very repetitive instructions. For instance, whenever you had to actually type in remarks for a particular report (say, RMK TORNADO 3SE MOV NE ) it would launch into a 1.5 minute spiel on how to enter text into the text box. And it would do it for every instance! For instance, the reports for Tornado, Thunderstorms, Hail, Volcanic Ash, and Virga are very similar. And each time, you had sit there while the thing babbled on about how to physically type the remarks.

Wednesday, April 25, 2007

Gun Control

I've been absolutely horrified by the events in Virginia Tech. Whenever 33 people die in an accident, it's a tragedy. But when 33 people are murdered executioner-style at point blank range by a deranged kid who should have been under pyschiatric care long ago, it's a tragedy of unspeakable proportions. I cannot imagine how the parents and families of the murdered children and teachers are handling the events, but I'm fairly certain the question in their minds is "Why? Why my son/ daughter/ brother/ sister/ father/ mother? What did they do to deserve this?" And that's a question I doubt we'll ever see answered.


I don't want to talk about the shooter - the media's already covered his story and his descent into madness. A lot of the focus, however, is on the fact that this person was obviously able to purchase two different types of firearms. From what I understand, he was under psychiatric care all of 1 day, so that may not have appeared for some reason. In addition, he had no prior criminal history.


Overall, I feel that gun control legislation works. 5 day waiting periods, required background checks, transfer systems for mail ordering guns - these are all checks and balances that have worked. I'm certain the waiting periods alone have eliminated a great number "crimes of passion".


I do find it interesting when others speculate how differently things would have turned out if one of the victims had a weapon of his own. I personally think that one of the reasons Cho chose a second school location was that he knew that everyone there would be unarmed and have no chance at stopping him.


I have a Concealed Carry license, and while I don't carry constantly, it is good to know that if I feel I am entering an uncomfortable situation I can bring a weapon along with me legally. I've had a gun pulled on me before; it's not fun, especially when you're unarmed. But I walked away. Unfortunately for the victims, VaTech's regulations prohibit bringing a weapon on campus . I don't blame them for the regulation - really, how many people do you think went to school that day expecting to be caught in a firefight? I still don't think guns should be allowed anywhere near a school campus, but those theories bring up interesting "what if's".


I just hope this tragedy doesn't bring around an overreaction from the gun control enthusiasts. Cho was a disturbed individual, and the tragedy here is that he was still on the street despite the numerous warning signs. It's not a good sign when your own grandfather is glad you're dead.

I've just seen too many news reports which make all gun owners appear like a bunch of whackjobs who go around randomly waving pistols at people. Gun control is not just about controlling who buys guns, it's about assuming personal responsibility for the weapons you have. All of the gun owners I know are rabidly responsible about their weapons and how they're handled. Unfortunately, it's the irresponsible minority that make the news.


I personally own a few guns which I've collected for their historical value. Most are Soviet World War II and Cold War pieces, which I consider interesting time capsules from bygone eras. All are pre-1970, with the youngest being a Makarov 9x18mm I use for Concealed Carry. Second to the pen, weapons have been the tool most responsible for changing the course of history - for better or for worse. I read a lot of non-fiction historical books; being able to own one of these pieces really brings history to life (pun intended).

I hope that the legislators and investigators focus on what the real problem was instead of laying blame on guns, or video games, or some other excuse to try and justify this kid's actions.

Wednesday, March 07, 2007

Getting Your Airplanes in a Twist

This has to be one of the funniest ATC clips I've ever heard. It's like a Who's on First with airliners.

Basically, the ground controller at New York City's John F. Kennedy airport winds up with a nice tangle of airplanes coming and going - and he's got to sort them out. Various Jet Blue, Alitalia, DHL, AirTran, Air France, and other carrier flights (with a corporate jet thrown in for fun:) ) wind up behind each other and pointed at each other. Lots of sarcasm and wit ensue.

Take a listen:
http://www.wickedpenguin.com/audio/JFKGround.mp3

And here's a visual aid:
JFK Airport Diagram

Wednesday, January 24, 2007

Real Air Traffic Control Video

I visited Miami TRACON on Jan. 19th, 2007 with a bunch of MDC students. Surprisingly enough, I was allowed to video tape inside the TRACON itself, with no restrictions. I got shots of the STARS simulators, the Traffic Management Unit (TMU), and - amazingly - controllers working live traffic.

Here is the footage I shot that day. I added a lot of text explanations in to the video, so that myself and others can use it to educate people as to what controllers actually do. It's a long-running joke that the public thinks ATC's are the guys with the earpads and lightsticks.

Here's my YouTube description of the video:
"A glimpse of a real air traffic control facility. Whenever you fly, folks like those shown in here are watching over you, making sure you arrive safely. It's a vital profession and, as you will see, requires a lot of concentration, skill, and judgement. I shot the video at Miami Tower on a class tour and edited it together, dropping in explanations for what is shown on screen. It starts off with their training simulator, then moves on to the 'real deal'."

Friday, January 19, 2007

Citation Runway Overshoot

Wow... talk about an illustrated manual on how to lose your pilot's license.

Step 1: Land an expensive corporate jet on a slick, short runway with a strong tailwind.

Step 2: Run said aircraft into the water off the runway end.

Step 3: Forget STEP ONE of your emergency checklist.

Friday, January 12, 2007

iPhone (aka iBroke or iShouldaBoughtaPS3)

So Apple just released their iPhone.

* Plays video. Check.
* Plays music. Check.
* Stores 4GB of data. Check.
* Full keyboard. Check.
* Has a touch screen. Check.
* Automatically detects if you're widescreen or portrait. Check.
* Built-in WiFi. Check.
* Capable browser, email, chat, and office software. Check.
* Bluetooth. Check.
* Built-in video-capable camera. Check.
* Nice looks. Check.
* Exchangeable battery with amazing longevity. Check.

Yeap, sounds good. Oh wait...that's right, I'm talking about my Cingular 8125 Windows Smartphone.

Which I bought last year.

For $300.

For the same price that they're selling the iPhone, I bought the 8125 as well as an Archos 504 with 4.5" widescreen and 80GB of media storage.

Go Cisco.

Monday, December 04, 2006

Pensacola-bound

So... I got assigned to Pensacola TRACON.

First reaction: Holy motherfracking God that's far.

Over 650 miles driving from where I live now, which translates into 12+ hours of driving or at least $360 in airfare per person. All other FAA facilities in Florida are within 6 hours of driving.

Second reaction: Good home prices, laid-back way of life, and lots of aviation-related activities.

We've been doing our homework and are really starting to like the area. The home prices are half of what they are here in Miami. And...the place is nice. Like, pleasant. Small-towny.

Sunday, December 03, 2006

Happy Webbed Feet


It was definitely not what was expected (cute and funny fluff), but as a big fan of penguins (my company's name is Wicked Penguin :P ) it had a good message and beautiful execution.

^ This needs to be a ride. :)

There's a saying that applies to this movie: "We have not inherited the Earth from our parents; we are borrowing it from our children." Many children have and are going to see this film, and I'm hoping that they and their parents realize that if things are going to be better in the future, then change needs to start now. I want to know that when I have grandkids many moons in the future, they'll still be able to see the funny flightless birds and the many other threatened species alive and well in their natural habitat.

Some things I liked (Spoilers of course):
  • All of the action scenes. They were amazingly shot, often with single cuts that lasted a minute or so at a time. Well choreographed, and really awe-inspiring, the seal chase, the skua fight, and the whale scene really had me on the edge of my seat, thinking "wow, that's cool". The one that ended with the huge ice wall cracking off (revealing the steam shovel) was especially incredible. I play around with Maya 7 for game mod development, but this movie really made me want to just delete Maya from my hard drive, LOL.
  • The scene where Mumble escapes from the skuas and jumps into the hole. After they leave, he's lying there alone, crying. That was just... heartbreaking. So cold, so alone, so scared - and no one to protect him, no one who even cared he was missing. I personally think it's on par with the "Mother?" scene from Bambi in creating a sense of despair and loneliness. That one shot really made the movie for me and made me want him to succeed.
  • The attention to natural detail. As a big fan of March of the Penguins, it felt as if I was watching an animated version of that. The environmental artists did a phenomenal job of capturing the surprising amount of textures, terrain, and windblown atmospheres that Antarctica can produce. The underwater and sea shots were also incredible. At times it felt as I was watching live-action footage.
  • The creature design was quite good. All of the animals were pretty close to being anatomically correct, except for some "cartoon embellishments* (bigger eyes, for instance) but overall looked very close to their natural counterparts. It's a far cry from, say, "Madagascar" where all of the animals were essentially caricatures.
  • Showing the natural cruelty of the Orcas/Killer Whales. Everyone associates Orcas with Shamu and cuteness, but in reality they're pretty sadistic creatures who enjoy beating the hell out of their prey for fun. That whole scene where they play ping-pong with the penguins around the frozen buoy gave me a real sense of deja vu from documentaries I've seen elsewhere. Just take a look at this: http://www.youtube.com/watch?v=ORjOmiluonc (notice that the seal in question is still alive throughout).
  • The five adelies rocked. They're my favorite penguin species and it was just cool to see the animators have some fun with their characters. And for those who were offended by the "Hispanic stereotypes", I'm Hispanic and live in a predominantly Hispanic city and wasn't offended in the least. They made every scene they were in and injected a lot of warmth and snappy humor.
  • The scene in the "Sea World" exhibit gave a (somewhat exagerrated) view on what happens to many animals in captivity. They lose their natural abilities to hunt and surive.
  • A different take on the common "be yourself" message. A lot of people here are saying the movie takes an anti-organized religion stance. I disagree. It's broader than that. To me it's message is that blind conformity can be stifling and that it's okay to question things if they hurt or ostracize innocent people. Many religions just happen to be guilty of that. There are of course the messages of tolerance and forgiveness which are always welcome.

Things I didn't like so much:

  • The parents' voices annoyed me. I got that they were supposed to be Elvis (Memphis, as in Graceland? :P ) and Marilyn Monroe (Norma Jean) but the mother's breathy voice sounded like she was trying too hard and ticked me off. I did like that detail of the mole on her chest. :P
  • The preachy ending. I like the message, but it was delivered a little too over-the-top. No one cares about penguins more than me, but... we get it - penguins need to survive, the world's nations need to regulate fishing, and we all need to get along. But there could have been a better and more subtle way of showing that than flash cuts of the United Nations and its various members arguing. However, it was good in showing that protecting the environment is a global issue that is prone to considerable argument.
  • Lack of progression from Mumble's time in captivity to when he arrives back at the rookery. One second he's indoors, the next he's right back home. I would have liked to at least seen a minute or two montage of footage showing how he went from captive to free.
  • Some of the pop songs were a bit annoying. "Shake your Bon Bon"...gag.

The Sexual Innuendos:
As far as the sexual innuendos everyone's going on about, get over it. If you're ticked off about your five year old knowing the real lyrics to "Let's talk about *eggs* , Baby" then *you* are the one that should be monitoring their radio or TV-watching. A normal five year old is only going to think they're talking about - you guessed it! - eggs. There are some definite sexual innuendos in the movie, but you'd have to be sexually knowledgable to get them. Some of them kind of pushed the envelope of what you'd normally see in an American animated movie, but none of them were any stronger than Shrek or its kin.

I know someone here mentioned that their kid was staring "wide-eyed at the screen" during the scene where Gloria and Mumble are falling all over each other in various positions. Did you think that maybe they were wide-eyed because the scene was funny, as opposed to your own dirty mind going off? If your 5 year old knows what the doggie-style position looks like and what you're doing while *in* that position, I'd suggest getting a channel blocker on the cable TV in your kid's room.

In Conclusion:
It's not a perfect movie, but it was definitely more good than bad. My wife and I had a good time watching it. I'll be buying the DVD whenever it comes out.

Saturday, November 18, 2006

Nail Biting

So the FAA's started calling Florida hires. An online acquaintance just got Palm Beach Tower. Another got Fort Lauderdale Tower. Oh crap.

With my luck, I'm getting a Level 6 Podunk Tower, Nowheresville, or worse... Tamiami...

/me rolls the dice.

C'mon! Gimme a FLL or an MIA... c'mon baby!

Monday, November 13, 2006

Aviatin'

In the past two weeks, I've done a couple of flights:

Sunday, October 29th: Mary and I flew to Stuart, FL out of Opa Locka. It was a great flight on a beautiful day. I mean, just absolutely gorgeous. We had a nice relaxing flight up on the west side of civilization, passing over miles and miles of empty Everglades.

We landed at Witham Airport in Stuart and got treated to a courtesy car via Galaxy Aviation. One of the ramp guys recommended a Mexican place down the way called Dos Amigos. We went there and enjoyed our "$100 burritos" ($90 per hour for the plane, $10 per person for the food :) ). Awesome food. We even took a container of salsa with us, it was so good.

On the way back, we flew down the east coast, passing directly over Palm Beach and Fort Lauderdale (with a near mid-air with a jet coming out of Boca). Mary slept most of the way back, since the dramamine had taken its toll and the espresso she had drunk wore off.

Sunday, November 5th: I got checked out in the diesel Cessna 172 down at ADF Airways. What an interesting plane. It's an entirely new way of flying!


  • First off, she's heavier by about 200 or so pounds than a regular 172, so carrying three people is iffy at best.
  • Secondly, she's got less power - 135 horsies as opposed to 180 in the 172SP. She tends to climb slower, though the instructor showed me that if I shoot for Vx (65 knots) instead of Vy (75 knots) she climbs pretty nicely.
  • Thirdly, most of her engine procedures are completely different. Instead of mixture or carb heat, you've got loadmeters, FADEC tests, digital LED readouts, and a single jet-like power lever.
  • She uses a constant speed prop, whose pitch is automatically controlled by the FADEC. You have to be gentle with power changes, since when you throttle up or back the pitch is automatically adjusted. As explained to me by the instructor, quick power changes result in "scary sounds". This reminded me a lot of the German WWII jet fighter, the Me262, whose engines would flameout if power was adjusted too abruptly.
  • As far as landing, it's totally different than a standard 172. In a standard 172, you can go idle abeam the numbers and do a short approach to the runway, with plenty of room to spare. On the diesel, when you cut that power she sinks like a stone. You need to think like a jet pilot: on approach, have power on at all times and only cut the power once the mains kiss the ground. The instructor suggested that this plane could almost be used as a transition aircraft for people moving on to light jets, since it's a similar power-on approach but at 1/2 half the airspeed.
  • The autopilot is a little quirky. It's a single axis (Heading) and we had some trouble getting it to work right. It synched up fine with the heading bug, but it didn't seem to respond when we set to GPS.
  • She's very, very efficient. We were cruising at 70% power, doing about 100 knots, and burning only 5 gallons per hour. Jet-A is also much cheaper than Avgas.
I love this plane. It's got a great interior, a great look, and it's just a cool piece of flying machine. I'm happy that not many people like it or are weirded out by it - it means more availability for me. :) The downside is that those who are checked out in it tend to take it for entire days at a time, since it's very efficient and comfortable.

"Sitting here in Limbo...

... but I know it won't be long /
Sitting here in limbo, like a bird without a song /
Well they're putting up resistance /
But I know that my faith will lead me on"

Jimmy Cliff is "the man".

No word from the FAA yet, but I've heard that they've made their selections. Time to chill out and just let it happen, while the drama continues in Washington and the FAA leadership continues spewing crap about there being no troubles within the workforce. My contacts amongst the ATC community say otherwise.

Some people on the ATCCTI.com board are starting to get calls and OKC dates, but most of them seemed to have graduated between December 2005 and May 2006. One girl says her OKC date was slotted for June 2007.