Flight #: 141 Commercial
Aircraft: Robinson R22 Beta II
Aircraft ID: N8361N
Duration, as PIC: 3.7hrs
Cumulative Time: 183.8hrs
Well, I've done it. Made it to the end of my Commercial Helicopter rating. You need 100 PiC (Pilot in command) hours for your commercial... and I had 3.7 yet to go. Well, as of tonight... done!
I really enjoy night flying. Night has to be great, since your margin for error gets pretty small at night, but when it is good... it is great. Tonight was perfectly clear, full moon, all goodness.
Nothing out of the ordinary to speak of on this flight. Only thing to note is how bored the PDX tower / controllers get at night. Really nothing landing or taking off at 12:30 am... so they like to talk and help out. In fact, I got VFR flight following from PDX most of the way since they had nothing better to do.
Now comes the FAA test.
Showing posts with label cross country. Show all posts
Showing posts with label cross country. Show all posts
Saturday, May 9, 2009
Friday, March 6, 2009
Solo X/C - Day - South
Flight #: 127 Commercial VFR61
Aircraft: Robinson R22
Aircraft ID: N2356T
Duration, as PIC: 1.5hrs
Cumulative Time: 160.6hrs
Another cross country solo flight... this time during the day. It was a beautiful day and just there just happened to be an open helicopter for me.
No real special stuff to note on the trip, except this time I decided that I wanted to circle some things to look at later. And, as you can see from the map below... I did.
You'll see a prison, a logging yard where the logs are stacked radially, and this really odd building up on a hill - in the middle of nowhere. I think it might be an insane asylum or possible a rehab for movie stars. Who knows.
View Larger Map
Aircraft: Robinson R22
Aircraft ID: N2356T
Duration, as PIC: 1.5hrs
Cumulative Time: 160.6hrs
Another cross country solo flight... this time during the day. It was a beautiful day and just there just happened to be an open helicopter for me.
No real special stuff to note on the trip, except this time I decided that I wanted to circle some things to look at later. And, as you can see from the map below... I did.
You'll see a prison, a logging yard where the logs are stacked radially, and this really odd building up on a hill - in the middle of nowhere. I think it might be an insane asylum or possible a rehab for movie stars. Who knows.
View Larger Map
Friday, February 20, 2009
Night Cross-Country Solo - a.k.a Heaven & Hell
Flight #: 125 Commercial VFR61
Aircraft: Robinson R22
Aircraft ID: N2223p
Duration, as PIC: 3.1hrs
Cumulative Time: 157.4hrs
First of all, I love night flying. On a clear night you can see incredible distances and you get to see amazing views of the city, towns and roads. Purely awe inspiring.
There are, obviously, negatives to night flight:
On the way down I decided to make a quick approach at Aurora (KUAO) airport. I've had a few approaches here in the past, but this was my first at night, so I felt relatively comfortable with the layout of the airfield.
I have to mention one of my favorite things about night flights... pilot controlled lighting. Basically, airport landing lights are just for aircraft landing at that local airport. No other reason for them. So, when there are no aircraft, no point for them to be on. Most airports will power down their lighting systems after XX minutes of innactivity on the radio. Basically, everything goes dark. (Except the airport beacon... you can see that flashing white-green from miles away.)
So, at night, on a speficic communications frequency, you can click your mic and turn on/off the airport lights. 3-clicks within 5 seconds = low intensity. 5 clicks within 5 seconds = medium intensity. 7 clicks within 5 seconds = high intensity.
There is something incredibly cool to be flying along... know the general location of the airport (from the rotating beacon), clicking your mic 7 times, then all of a sudden a full airport lighting system comes on to welcome you. Obviously the bigger the airport, the cooler it is... but still, even at a little airport like Aurora... it is cool.
So, as long as nobody is near the airport with me... I will put the lights on full for an approach. After I turn downwind, put them on low (or off), then put them back on high as I turn base. Kind of childish, I suppose. But it is really cool to turn final and click on the lights and see it just jump up out of nowhere.
Cheap date.
After departure, I headed down to Salem (KSLE). Salem is a Class-Delta airspace, so you are required to get permission to enter their airspace. It is good practice to enter these airspace from time to time. Luckily, Hillsboro is also a Delta airspace, so I'm used to the back and forth communications. On the way in they had me come in rather close to the runway and I obliged. They then told me that if I could make it, I was able to do a quick / hard right turn... followed by a hard left to make a direct in approach to the runway. Being a helicopter, this was no issue. I did a few approaches, and then headed down to Albany (KSLE)
This is where the fun began. Another Hillsboro student / CFI were doing their first night cross country flight here, and I could recognize their voices. I joined the pattern and made a few appraoches, but also noticed that there was another helicopter on the ground, in front of the 24 hr, self-serve fuel pump. No big deal... happens all the time. I'd just wait my turn.
Well, as it turns out, this person happened to have an overspeed. A serious overspeed during the run-up after getting fuel and could not fly the helicopter from that point on. Why? Well, lemme tell you. Pull up a chair, sit back...
The main rotor blades are mounted to the mast via a series of bearings and hinges. The outward force, directed along the length of the blade, is proportional to the speed at which the blades rotate around the central hub. The faster the rotation, the more force there is trying to pull the blades out of the hub. To allow the pilot to still be able to conrol the pitch of the rotor blades with the cyclic, there have to be bearings at that rotor/hub junction. Apply too much force at that joint, you could have blade seperation (rare) or serious damage to the bearing itself (common). This damage is called Brinelling. Think of it as the internal hub bearings being stressed to the point where they either crush, or dent the inner/outer surfaces of the bearing itself. Basically... bad. Real bad thing to have happen to you.
If you get an overspeed with 100% - 104% rotor RPM, things are egenerally fine. The helcopter (Robinson R22) can take it... and you don't have much to be concerned about. 104% - 110%, you need to shut down, and have the helicopter inspected. >110%... is really bad. Basically, the aircraft it completly torn down, and sometimes requires that the ship be sent back to the factory for an overhaul. At that speed, they have to check, not only the rotor blades, bearings and hub, but they have to check every bit of the drive train as well. Everything has to be going over-max speed to get the rotors going that fast.
Lets just say, you do not want an overspeed of any kind. Definitely not one >110%. This one was "well above 110%". The result of all of this... that helicopter was not going to be moving from the spot that it was in... directly in front of the refueling station. Which meant... I was not going to be refueling the helicopter at Albany as planned.
So, I headed back to Salem to refuel. Certain Delta airports close down at certain times... Salem shuts down, converts to Echo airspace, at 10:30pm. The first time I was here, it was a Delta airspace, now it was Echo. Basically, no tower to help me find the fuel pump.
So, being a helicopter, it really is not that big of a deal... you just go searching. Off in the distance I found a nice, bit BP sign and headed that way. As it turns out, this is a mega-self-service pump with multiple hoses, and the other student/CFI who I saw in Albany were there doing the same thing. We chatted a bit, stretched and refueled.
By the way, the seats in the R22 suck. After about 90 minutes, your ass is numb. But, you are flying a helicopter... so things could be worse.
I finished up first, and headed out... back to Hillsboro. Back with the pilot controlled lighting. But, this time, I was at a big airport, with real lights and approach lighting systems. So, 7-clicks, and the world just lit up. Taxiway lights, approach lighting systems, all kinds of cool stuff. Thrills!
Headed north, as usual. Now, as I mentioned before, wind gets a little weird at night around here. I expected to run into a few bumps on my way back when I hit the 217N & I5N intersection. And boy did I.
I am, in general, not a motion sick kind of person. I have been on plenty of boats, car rides, airplane rides to know what turbulence is... how you just have to take your knocks... and move on. This was different. I was sick as a dog - this was horrible. I can honestly say, I have never been in such a bad batch of turbulence in my life... let along behind the stick at the time. After the fact I checked the wind in the area (local airports had minimal wind), but right at that spot... 20knot gusts. PDX, after I landed, had 30 knot gusts. Now, that kind of wind sucks in general... let alone in a tiny R22.
I swear I was getting knocked around like I was in a inflatable raft on the open ocean. I would yaw 30º in either direction. +50 feet, -50 feet in altitude. My speed would jump from 60kias to 40kias in a second.... then jump up to 75kias. Really, sucked. About halfway in, I had to make a real decision about what I was going to do. Would I make an emergency landing? What if I puked? Finally I decided to pick out two points of decent spot for an emergency landing. If I made it to the first, I would pick one just on the other side of the second and limp my way along. If I puked... I would just do it right in my own lap, and clean up afterwards. Twice I thought... "Ok, this is it... I'm going to boot."
Now, everyone knows that fresh air helps when you are nauseous. What about 2º air at approximately 60 knots? Sure, it helps, but you freeze too. So, I opted for uncontrollable shivering rather than puking on myself. Nice choices.
Anyway, I made it back to the airport safe... which, in the end, is all that matters. But, it sucked.
I landed, post-flighted the helicopter, and stuffed the helicopter log-book into a door slot and went home. Sandy greeted me at the door and said I looked "really green, are you OK?".
As Sandy pointed out, there is a good thing as a result of the last 15 minutes of flight... "You know your limit now... you can do it again if you had to, and you know the outcome." She is absolutely right.
I would certainly never intentionally go through that again, but if circumstances forced me there again, I'd make it through. Puke / Emergency free.
View Larger Map
Aircraft: Robinson R22
Aircraft ID: N2223p
Duration, as PIC: 3.1hrs
Cumulative Time: 157.4hrs
First of all, I love night flying. On a clear night you can see incredible distances and you get to see amazing views of the city, towns and roads. Purely awe inspiring.
There are, obviously, negatives to night flight:
- emergency landing spots - hard to see good ones... simple as that.
- clouds / mist - again, hard to see them.
- obstacles - yet again, can't to see them in time.
- distance estimation - at night, your depth perception is off... so it is hard to judge distances and altitudes. Coming in to land is rather tricky as you can't really tell where the ground is. All you get to see is two hyper-bright spots where your headlights meet the ground. I happen to come in to a high hover each time. Practice.
- weird wind patterns - as the earth cools down, you get some changes in wind... and as I found out on this flight... it can be a really big deal.
On the way down I decided to make a quick approach at Aurora (KUAO) airport. I've had a few approaches here in the past, but this was my first at night, so I felt relatively comfortable with the layout of the airfield.
I have to mention one of my favorite things about night flights... pilot controlled lighting. Basically, airport landing lights are just for aircraft landing at that local airport. No other reason for them. So, when there are no aircraft, no point for them to be on. Most airports will power down their lighting systems after XX minutes of innactivity on the radio. Basically, everything goes dark. (Except the airport beacon... you can see that flashing white-green from miles away.)
So, at night, on a speficic communications frequency, you can click your mic and turn on/off the airport lights. 3-clicks within 5 seconds = low intensity. 5 clicks within 5 seconds = medium intensity. 7 clicks within 5 seconds = high intensity.
There is something incredibly cool to be flying along... know the general location of the airport (from the rotating beacon), clicking your mic 7 times, then all of a sudden a full airport lighting system comes on to welcome you. Obviously the bigger the airport, the cooler it is... but still, even at a little airport like Aurora... it is cool.
So, as long as nobody is near the airport with me... I will put the lights on full for an approach. After I turn downwind, put them on low (or off), then put them back on high as I turn base. Kind of childish, I suppose. But it is really cool to turn final and click on the lights and see it just jump up out of nowhere.
Cheap date.
After departure, I headed down to Salem (KSLE). Salem is a Class-Delta airspace, so you are required to get permission to enter their airspace. It is good practice to enter these airspace from time to time. Luckily, Hillsboro is also a Delta airspace, so I'm used to the back and forth communications. On the way in they had me come in rather close to the runway and I obliged. They then told me that if I could make it, I was able to do a quick / hard right turn... followed by a hard left to make a direct in approach to the runway. Being a helicopter, this was no issue. I did a few approaches, and then headed down to Albany (KSLE)
This is where the fun began. Another Hillsboro student / CFI were doing their first night cross country flight here, and I could recognize their voices. I joined the pattern and made a few appraoches, but also noticed that there was another helicopter on the ground, in front of the 24 hr, self-serve fuel pump. No big deal... happens all the time. I'd just wait my turn.
Well, as it turns out, this person happened to have an overspeed. A serious overspeed during the run-up after getting fuel and could not fly the helicopter from that point on. Why? Well, lemme tell you. Pull up a chair, sit back...
The main rotor blades are mounted to the mast via a series of bearings and hinges. The outward force, directed along the length of the blade, is proportional to the speed at which the blades rotate around the central hub. The faster the rotation, the more force there is trying to pull the blades out of the hub. To allow the pilot to still be able to conrol the pitch of the rotor blades with the cyclic, there have to be bearings at that rotor/hub junction. Apply too much force at that joint, you could have blade seperation (rare) or serious damage to the bearing itself (common). This damage is called Brinelling. Think of it as the internal hub bearings being stressed to the point where they either crush, or dent the inner/outer surfaces of the bearing itself. Basically... bad. Real bad thing to have happen to you.
If you get an overspeed with 100% - 104% rotor RPM, things are egenerally fine. The helcopter (Robinson R22) can take it... and you don't have much to be concerned about. 104% - 110%, you need to shut down, and have the helicopter inspected. >110%... is really bad. Basically, the aircraft it completly torn down, and sometimes requires that the ship be sent back to the factory for an overhaul. At that speed, they have to check, not only the rotor blades, bearings and hub, but they have to check every bit of the drive train as well. Everything has to be going over-max speed to get the rotors going that fast.
Lets just say, you do not want an overspeed of any kind. Definitely not one >110%. This one was "well above 110%". The result of all of this... that helicopter was not going to be moving from the spot that it was in... directly in front of the refueling station. Which meant... I was not going to be refueling the helicopter at Albany as planned.
So, I headed back to Salem to refuel. Certain Delta airports close down at certain times... Salem shuts down, converts to Echo airspace, at 10:30pm. The first time I was here, it was a Delta airspace, now it was Echo. Basically, no tower to help me find the fuel pump.
So, being a helicopter, it really is not that big of a deal... you just go searching. Off in the distance I found a nice, bit BP sign and headed that way. As it turns out, this is a mega-self-service pump with multiple hoses, and the other student/CFI who I saw in Albany were there doing the same thing. We chatted a bit, stretched and refueled.
By the way, the seats in the R22 suck. After about 90 minutes, your ass is numb. But, you are flying a helicopter... so things could be worse.
I finished up first, and headed out... back to Hillsboro. Back with the pilot controlled lighting. But, this time, I was at a big airport, with real lights and approach lighting systems. So, 7-clicks, and the world just lit up. Taxiway lights, approach lighting systems, all kinds of cool stuff. Thrills!
Headed north, as usual. Now, as I mentioned before, wind gets a little weird at night around here. I expected to run into a few bumps on my way back when I hit the 217N & I5N intersection. And boy did I.
I am, in general, not a motion sick kind of person. I have been on plenty of boats, car rides, airplane rides to know what turbulence is... how you just have to take your knocks... and move on. This was different. I was sick as a dog - this was horrible. I can honestly say, I have never been in such a bad batch of turbulence in my life... let along behind the stick at the time. After the fact I checked the wind in the area (local airports had minimal wind), but right at that spot... 20knot gusts. PDX, after I landed, had 30 knot gusts. Now, that kind of wind sucks in general... let alone in a tiny R22.
I swear I was getting knocked around like I was in a inflatable raft on the open ocean. I would yaw 30º in either direction. +50 feet, -50 feet in altitude. My speed would jump from 60kias to 40kias in a second.... then jump up to 75kias. Really, sucked. About halfway in, I had to make a real decision about what I was going to do. Would I make an emergency landing? What if I puked? Finally I decided to pick out two points of decent spot for an emergency landing. If I made it to the first, I would pick one just on the other side of the second and limp my way along. If I puked... I would just do it right in my own lap, and clean up afterwards. Twice I thought... "Ok, this is it... I'm going to boot."
Now, everyone knows that fresh air helps when you are nauseous. What about 2º air at approximately 60 knots? Sure, it helps, but you freeze too. So, I opted for uncontrollable shivering rather than puking on myself. Nice choices.
Anyway, I made it back to the airport safe... which, in the end, is all that matters. But, it sucked.
I landed, post-flighted the helicopter, and stuffed the helicopter log-book into a door slot and went home. Sandy greeted me at the door and said I looked "really green, are you OK?".
As Sandy pointed out, there is a good thing as a result of the last 15 minutes of flight... "You know your limit now... you can do it again if you had to, and you know the outcome." She is absolutely right.
I would certainly never intentionally go through that again, but if circumstances forced me there again, I'd make it through. Puke / Emergency free.
View Larger Map
Monday, January 19, 2009
Long cross-country to the coast...
Flight #: 116 [Commercial VFR61]
CFI: Kristie E.
Aircraft: Robinson R22 Beta II
Aircraft ID: N779SH
Duration, as PIC: 4.1hrs
Cumulative Time: 142.0hrs
I'm going to do this blog post with minimal text. Just three words to describe it:
Leg 1 of 3: Hillsboro (KHIO) to Tillamook (KTMK)
View Larger Map
Leg 2 of 3: Tillamook (KTMK) to Independence (7S5)
View Larger Map
Leg 3 of 3: Independence (7S5) to Hillsboro (KHIO)
Sadly, the battery in my iPhone died. Have to fake it a bit.
View Larger Map
CFI: Kristie E.
Aircraft: Robinson R22 Beta II
Aircraft ID: N779SH
Duration, as PIC: 4.1hrs
Cumulative Time: 142.0hrs
I'm going to do this blog post with minimal text. Just three words to describe it:
IT
WAS
AWESOME
WAS
AWESOME
Leg 1 of 3: Hillsboro (KHIO) to Tillamook (KTMK)
View Larger Map
Leg 2 of 3: Tillamook (KTMK) to Independence (7S5)
View Larger Map
Leg 3 of 3: Independence (7S5) to Hillsboro (KHIO)
Sadly, the battery in my iPhone died. Have to fake it a bit.
View Larger Map
Friday, January 2, 2009
Solo, Live ATC Streaming Radio, GPS Tracks
Flight #: 114 [Commercial VFR61]
Aircraft: Robinson R22 Beta II
Aircraft ID: N2304W
Duration, as PIC: 1.1hrs
Cumulative Time: 136.5hrs
Been quite a while since a blog post. It's not that I'm losing interest in flying or anything, it is purely a perfect storm of Oregon weather, holidays and maintenance.
Oregon weather this time of year just plain sucks. Really, it is the inconsistency that gets you. Some days, like right now, it is cool and sunny. Others, rain. Others, pure white-out of clouds. Blech!
Holidays... friends, family and just fun take up time - and they get priority.
Maintenance... there had been a few times where friends or family wanted to go up for a spin, but depending on out combined weight, we would only be able to fly in the "Flying Tractor" a.k.a. the Schewizer 300CB. That sucker went in for its 100hr maintenance rebuild. There are very few people that fly the tractor, so it does not get priority... and so it sat. Almost 8 weeks.
Solo:
Anyway, I FINALLY got up the other day. Kind of a crazy day, actually. The weather was cold, a little windy, but relatively clear.
Headed out to, what is now a pretty common and mindless run for me, Portland Mulino Airport. 25nm South East of the airport. Takes you over some nice areas... and this is generally the flight I take friends on. The less "work" I have to do to fly, the more I can relax. A new place... I need 100% concentration and I can't answer any of the "hey, what is that?" type questions from passengers. It is their first flight, they could care less where we are going.
Anyway, good flight out. Ran in to some nimrod fixed wing dude who got his runways mixed up and was landing the wrong direction... wind at his tail. So, I had to loop around and wait for him to figure it out - with some help from me. Did a few patterns, headed back. As soon as I started looking North West, I noticed a serious weather cell coming in... and it appeared to be about 20nm west of HIO. I tried to tune in ATIS (Weather Reporting) for KHIO, but was getting too much static, so had to climb a little to listen in. Things sounded fine, so I headed back, via UAO, like I normally would. About 10nm from Mulio, I tried ATIS again, but things had not yet changed... however, the cell seemed to be quite a bit closer and looked really ominous. I tuned in to the tower frequency and heard them talking about gusts etc.
It was at this point where I decided to high-tail it back to the airport to see if I could stay ahead of the weather. I figured I had about 15 minutes before it hit... and I needed less than 10 to get there. Nosed 04W down, and brought it up to about 90kias and headed in. I was rather high at the time, 2500ft, and I started to encounter some precipitation, not freezing yet, but close. Then a few flakes started to hit the windscreen. We've been taught to have a real eye for ice. Not only does ice add extra weight to an aircraft... it spoils the aerodynamics. If you get build-up on the rotors... bad news. The last thing you want is your rotor lift efficiency to decrease.
So, we're taught to keep an eye on droplets on the window... do they freeze? Then, you also continually look at your skids. They are easily visible from the pilot seat, are direct into the wind, cold metal, and will get ice (most of the time) before any other part... especially any moving part. No ice, but I did not feel like taking any chances so I descended to about 700ft. The lower you go the warmer it should be... but the less time you have if you run in to an engine issue and need to execute an emergency landing. Hunch paid off, and things started to warm up and I was left with a little bit of spitting rain.
So, not going to ice up, but that weather cell was getting really serious. I was on Tower Frequency and they started talking about wind changing directions, gusts to 15knots. Not really dangerous stuff... yet, but it was certainly not the best choice of landing weather.
I requested access to the airspace, was granted and came in. On my way in, I started hearing chatter on the radio about the field "going IFR" (weather conditions bad enough to require special instrumentation and training). Luckily I was in a hover right off the end of my landing spot when the field did go IFR.
So, little bit of excitement.
Couple cool things as a result of this flight. I found Live ATC broadcasts, and recordings. This site broadcasts tower communications over net radio. So, you can listen in to the chatter for almost any towered airport. fly-geek, I know, but still cool. If you want to listen in to Portland-Hillsboro Airport (KHIO), you just search, or click this link.
The really cool part of it is that they archive the streams as MP3 files for up to 30 days. And, well, here is the audio from the 2nd half of the flight - the return. Apparently the feed was down for the first part, but that's fine since I was just requesting a south departure.
If you are interested, take a listen. I've noted (above) the approximate time into the MP3 file these comms happen. I'm pretty sure I'm going to be downloading ALL my flights recordings from now on.
Live ATC Streaming Radio
GPS Tracks:
So far, I've been estimating my flight tracks with Google Maps, and their ability to superimpose a line over a particular map. I've done that here with this flight:
View Larger Map
The fun thing is that I've just purchased ($7.99) a great little iPhone Application, MotionX GPS. (iTunes Download) Anyway, it allows you to track, to a very high accuracy, the location of your phone, save the points, and then post them up on Google Maps to provide a very accurate map of where you have been. So, I set it up, throw it in my jacket pocket, and off I go.
Now, it would be really cool if I knew how to use the application before this flight... cause I have a really impressive GPS track of me walking out to the aircraft. Next time, I know what to do, and it will be sooooo cool.
Aircraft: Robinson R22 Beta II
Aircraft ID: N2304W
Duration, as PIC: 1.1hrs
Cumulative Time: 136.5hrs
Been quite a while since a blog post. It's not that I'm losing interest in flying or anything, it is purely a perfect storm of Oregon weather, holidays and maintenance.
Oregon weather this time of year just plain sucks. Really, it is the inconsistency that gets you. Some days, like right now, it is cool and sunny. Others, rain. Others, pure white-out of clouds. Blech!
Holidays... friends, family and just fun take up time - and they get priority.
Maintenance... there had been a few times where friends or family wanted to go up for a spin, but depending on out combined weight, we would only be able to fly in the "Flying Tractor" a.k.a. the Schewizer 300CB. That sucker went in for its 100hr maintenance rebuild. There are very few people that fly the tractor, so it does not get priority... and so it sat. Almost 8 weeks.
Solo:
Anyway, I FINALLY got up the other day. Kind of a crazy day, actually. The weather was cold, a little windy, but relatively clear.
Headed out to, what is now a pretty common and mindless run for me, Portland Mulino Airport. 25nm South East of the airport. Takes you over some nice areas... and this is generally the flight I take friends on. The less "work" I have to do to fly, the more I can relax. A new place... I need 100% concentration and I can't answer any of the "hey, what is that?" type questions from passengers. It is their first flight, they could care less where we are going.
Anyway, good flight out. Ran in to some nimrod fixed wing dude who got his runways mixed up and was landing the wrong direction... wind at his tail. So, I had to loop around and wait for him to figure it out - with some help from me. Did a few patterns, headed back. As soon as I started looking North West, I noticed a serious weather cell coming in... and it appeared to be about 20nm west of HIO. I tried to tune in ATIS (Weather Reporting) for KHIO, but was getting too much static, so had to climb a little to listen in. Things sounded fine, so I headed back, via UAO, like I normally would. About 10nm from Mulio, I tried ATIS again, but things had not yet changed... however, the cell seemed to be quite a bit closer and looked really ominous. I tuned in to the tower frequency and heard them talking about gusts etc.
It was at this point where I decided to high-tail it back to the airport to see if I could stay ahead of the weather. I figured I had about 15 minutes before it hit... and I needed less than 10 to get there. Nosed 04W down, and brought it up to about 90kias and headed in. I was rather high at the time, 2500ft, and I started to encounter some precipitation, not freezing yet, but close. Then a few flakes started to hit the windscreen. We've been taught to have a real eye for ice. Not only does ice add extra weight to an aircraft... it spoils the aerodynamics. If you get build-up on the rotors... bad news. The last thing you want is your rotor lift efficiency to decrease.
So, we're taught to keep an eye on droplets on the window... do they freeze? Then, you also continually look at your skids. They are easily visible from the pilot seat, are direct into the wind, cold metal, and will get ice (most of the time) before any other part... especially any moving part. No ice, but I did not feel like taking any chances so I descended to about 700ft. The lower you go the warmer it should be... but the less time you have if you run in to an engine issue and need to execute an emergency landing. Hunch paid off, and things started to warm up and I was left with a little bit of spitting rain.
So, not going to ice up, but that weather cell was getting really serious. I was on Tower Frequency and they started talking about wind changing directions, gusts to 15knots. Not really dangerous stuff... yet, but it was certainly not the best choice of landing weather.
I requested access to the airspace, was granted and came in. On my way in, I started hearing chatter on the radio about the field "going IFR" (weather conditions bad enough to require special instrumentation and training). Luckily I was in a hover right off the end of my landing spot when the field did go IFR.
So, little bit of excitement.
Couple cool things as a result of this flight. I found Live ATC broadcasts, and recordings. This site broadcasts tower communications over net radio. So, you can listen in to the chatter for almost any towered airport. fly-geek, I know, but still cool. If you want to listen in to Portland-Hillsboro Airport (KHIO), you just search, or click this link.
The really cool part of it is that they archive the streams as MP3 files for up to 30 days. And, well, here is the audio from the 2nd half of the flight - the return. Apparently the feed was down for the first part, but that's fine since I was just requesting a south departure.
@3:20
Me: "Hillsboro Tower, Helicopter 2304W, 7 miles south with Siera. Request parking."
Tower: "Winds calm. Correction, Wind 260 at 15. Helicopter 2304W, Hillsboro Tower. Report 1 mile south."
Me: "Report 1 south, 04W."
@5:49
Me: "04W is 1 mile south."
Tower: "Helicopter 04W, not in sight, proceed to HAI"
Me: "Proceed to HAI, 04W."
If you are interested, take a listen. I've noted (above) the approximate time into the MP3 file these comms happen. I'm pretty sure I'm going to be downloading ALL my flights recordings from now on.
Live ATC Streaming Radio
GPS Tracks:
So far, I've been estimating my flight tracks with Google Maps, and their ability to superimpose a line over a particular map. I've done that here with this flight:
View Larger Map
The fun thing is that I've just purchased ($7.99) a great little iPhone Application, MotionX GPS. (iTunes Download) Anyway, it allows you to track, to a very high accuracy, the location of your phone, save the points, and then post them up on Google Maps to provide a very accurate map of where you have been. So, I set it up, throw it in my jacket pocket, and off I go.
Now, it would be really cool if I knew how to use the application before this flight... cause I have a really impressive GPS track of me walking out to the aircraft. Next time, I know what to do, and it will be sooooo cool.
Monday, November 24, 2008
Solo X/C to Kelso - Just for fun.
Flight #: 111 [Commercial VFR61]
Aircraft: Robinson R22 Beta II
Aircraft ID: N227SH
Duration, as PIC: 1.2hrs
Cumulative Time: 135.4hrs
Got a call this morning that told me there was an open helicopter - if I wanted it. Hell, yea!
So, did my pre-flight planning (Weight and Balance, Weather Check, Flight Manifest, and filed my flight plan with Seattle Flight Service) and sped out the door. 227SH was sitting there waiting for me with 47.5 hours left before maintenance - so it was in prime condition.
Day was perfect; cold, little bit of wind from the west and clear to 25k ft.
Nothing particular to speak of, other than the fact that I know understand the frustration our CFIs go though listening to us murder communications - particularly in uncontrolled airports. It is pretty bad. I felt, however, pretty damn good since I was noticing the problems.
You just can't beat the feeling of flying.
Aircraft: Robinson R22 Beta II
Aircraft ID: N227SH
Duration, as PIC: 1.2hrs
Cumulative Time: 135.4hrs
Got a call this morning that told me there was an open helicopter - if I wanted it. Hell, yea!
So, did my pre-flight planning (Weight and Balance, Weather Check, Flight Manifest, and filed my flight plan with Seattle Flight Service) and sped out the door. 227SH was sitting there waiting for me with 47.5 hours left before maintenance - so it was in prime condition.
Day was perfect; cold, little bit of wind from the west and clear to 25k ft.
Nothing particular to speak of, other than the fact that I know understand the frustration our CFIs go though listening to us murder communications - particularly in uncontrolled airports. It is pretty bad. I felt, however, pretty damn good since I was noticing the problems.
You just can't beat the feeling of flying.
Sunday, August 3, 2008
Frustration, thy name is ABBA
Flight #: 086 [Commercial VFR61]
CFI: Kristie E.
Aircraft: Robinson R22 Beta II
Aircraft ID: N956SH
Duration, as PIC: 1.5hrs
Cumulative Time: 104.5hrs
See the airport in this picture?
No? Really, it is right there. I swear. How about this... you fly 40 minutes to this friggin' airport that some joker named ABBA, btw, to prove how you can find things. Well, I fly around in circles... looking for the airport. NW of the town of Sheridan, OR and at 200ft. Looking, looking.
Give Up?
Scroll down...
Little more...
Take a look.
Airport my ass. I found it, eventually tho... so there is a bit of positive. Stupid ABBA.
CFI: Kristie E.
Aircraft: Robinson R22 Beta II
Aircraft ID: N956SH
Duration, as PIC: 1.5hrs
Cumulative Time: 104.5hrs
See the airport in this picture?
No? Really, it is right there. I swear. How about this... you fly 40 minutes to this friggin' airport that some joker named ABBA, btw, to prove how you can find things. Well, I fly around in circles... looking for the airport. NW of the town of Sheridan, OR and at 200ft. Looking, looking.
Give Up?
Scroll down...
Little more...
Take a look.
Airport my ass. I found it, eventually tho... so there is a bit of positive. Stupid ABBA.
Saturday, August 2, 2008
Morning Solo
Flight #: 085 [Commercial VFR61]
Aircraft: Robinson R22 Beta II
Aircraft ID: N2548S
Duration, as PIC: 1.1hrs
Cumulative Time: 103.0hrs
Wanted to get some solo time in... so I just signed up for it. See, I get to do that now that I'm certified as a helicopter pilot. I get a real kick out of saying that; I'm a helicopter pilot. :)
No thrills, no surprises. Just a 8:00am flight through some beautiful Oregon countryside with the sunrise.
I tell ya, one hell of a way to start the say.
Aircraft: Robinson R22 Beta II
Aircraft ID: N2548S
Duration, as PIC: 1.1hrs
Cumulative Time: 103.0hrs
Wanted to get some solo time in... so I just signed up for it. See, I get to do that now that I'm certified as a helicopter pilot. I get a real kick out of saying that; I'm a helicopter pilot. :)
No thrills, no surprises. Just a 8:00am flight through some beautiful Oregon countryside with the sunrise.
I tell ya, one hell of a way to start the say.
Saturday, March 15, 2008
Triangle of Lost - The full story.
Ok, so I was shaken, grumpy and pissed off after my last XC flight. I got lost, and I hate that. I suppose I really did not feel like talking about it too much. But, I thought about it a lot, and will guarantee that I will NOT get lost on that flight again. I've spent the last few days reading over the all the airports within a reasonable distance and looking both on the sectional map, and Google's satellite imagery.
So, here is the full story. How I got in, how I got out, etc. (Mainly for you, Bob. :)
The planned flight plan is as shown here:
HIO is at the 12 O'Clock position, Mulino at 4 O'Clock, McMinneville at the 7 O'Clock. The part I'm interested in here is at the lower portion of the triangle. So, lets zoom a bit:
So, it all started as I was entering the airspace for Mulino airport (green arrow). There was a 9 knot wind blowing from 130º (black arrow).
When you do your flight planning, you need to know about your airports. Their traffic patterns, runway lengths and directions, etc. Well, I did all that. I knew that Mulino had one runway strip, labeled Runway 14 and Runway 32. If you didn't know, they name the runways so that you can tell which direction they are facing. In this case, oriented to 140º and 320º, respectively.
So, anyway, I knew this. And since you want to land into the wind, whenever possible, the airports with a control tower will select the appropriate runway for you. In this case, there was no tower, so you have to rely on your knowledge, and the knowledge of the other people flying in the airport. The active runway is suppose to be Runway 14 with the wind coming from 130º. It just is. It also happens to be a right air traffic pattern runway. This means, that you are supposed to make right hand turns all the way to landing. Since I was coming in from the North West, I could have, technically come right in to the runway, almost straight on. But, that's not the cool thing to do. You are supposed to enter the downwind leg at 45º and make your right turns in. The image below shows a left pattern, but you get the idea. Just flip it so that you would land making right turns:
In my case, I would have to fly past the airport to the west, make a wide left turn so as to come in at 45º on the downwind leg and then enter the pattern. As a side note, while you always want to check the weather system broadcast in the area, you only trust what you can see. And luckily for me, there were a few wind indicators in the are for me to look at. Things like wind socks are always nice near an airport... but out west here, people tend to burn leaves and brush. And this day there were two fires going within about 1/2 mile of the runway. So, I was 100% sure of the wind. So, I broadcast my intention to "enter the right-downwind for Taxiway 14". We can land on taxiways or runways. It's cool of us not to take up runway space... and it is safer too.
Ok, enough background. So, I veer off to the right of runway 14 to make my wide left turn into the pattern when we see some dude in an airplane taking off on runway 32. The opposite direction on the runway. Taking off with a 9 knot tail wind. Not smart. Not to mention dangerous. So, I do a go around, and make a right hand turn to re-enter on the downwind. As I get about 270º in my turn, this dude that just took off cuts hard left and comes way too close to my flight path. Granted, I was at 800ft (as I'm suposed to be) and he was probably climbing past 1200, but still... not cool dude. So, I re-announce where I am, and what I'm doing. This wakes the airplane dude up, I guess, and he broadcast a quick "sorry about that, did not see you guys there". Huh? Really? I'm in a bright red helicopter with a giant rotating blade with my lights on... exactly where I said I would be. But, ok... fine. Stuff happens, and we were really not that close.
So, I do another go around. And we hear, on the radio another fixed winger come on the radio " at 1000ft, on the right downwind for runway 32." Kristy says "Screw this place, get us out of here." Basically another dude in an airplane was using the wrong runway, again. This time for a landing. But, rather than making left patterns for runway 32, as he is supposed to do, he's doing right ones. What a mess.
I turn off to the west and we just skip this approach at Mulino. In hindsight, we should have come on the radio with a "Mulino traffic, wind indicators clearly show that runway 14 should be in operation, not 32. Please check wind." But, we didn't. Totally one of those things you think of 5 minutes after you need it. But, all is well, and we're headed north west to Aurora with a bit of a tailwind.
A few minutes in to this leg Kristy says, "The FAA just called there is an accident in Aurora, divert to Lenhardt". Obviously the FAA did not call, she was just giving me a scenario to deal with. I didn't know where Lendhart was, so I had to look a little on the map. (To save you some time, it is the red arrow.)
So, I look it up on the map, estimate my course and direction and head to Lendhart. Eventually I see it off to the left, quite a ways away. I point it out to Kristy, and she gives me the OK to head to McMinneville. So, looking at the map, I head due west. I forgot to correct for wind... and this was my big flaw. I was heading NW. A lot more north than I expected, at least. I also think the wind had picked up a little, cause, as you will see, I was way off.
I was flying along to my next checkpoint, a significant bend in the river. What I was looking for is the blue circled area below. What I was flying over was the red circled area. I was way north of where I wanted to be. As I crossed the river, I saw this town... which, according to my plan, is not supposed to be there. As you can see, it was the town of Newberg. But, when I planned this out, I was not supposed to cross the river and see a town. So, wham, I'm lost.
The lost procedures are "the 5 C's". Calm, Climb, Circle, Calculate, Communicate. So, I take a deep breath, start climbing, and start doing a right hand circle. I start looking at the land, my map, etc. I find a significant feature on the ground below me, an island in the river. OK, great, there has to be an island on the map. So, I look, where I think I'm supposed to be... the blue circle. No island on the map. Shit. So, I conclude that either the island is not big enough to be on the map, or else I'm nowhere near this point on the map. First thing I do is look for an island in the river elsewhere on the map. And I don't see anything withing a reasonable flying distance. So, I'm now sure that this island I'm circling over, now at 3000ft, must not be big enough to show up.
So, screw this river, I think... now I'll look for a town. I should be seeing St. Paul to my south. (Remember, I think I'm in the blue, but am actually in the red circle). Nope, no St. Paul. Only this huge town to the north of the river. Could I be seeing Lafayette? Dayton? Where the F am I! Kristy is with me, of course, and being very calm. She knows exactly where we are... just wants me to struggle through. Which, is a great teaching tool, but it pissed me off. I'm now at 4000ft, circling like a moron, getting all twisted up.
Finally she speak up and says, "What are you using for your fix?" and I said, mention that I'm looking for the island in the river as well as the direction of the bend. "Are you looking for a 'C' to the east or a 'n' shaped bend to the south?". I believe I'm in the blue, so I'm looking for a 'C' to the east, but I'm actually in the red over a 'n' to the south.
This helps, obviously, and I suddenly realize I'm about 10nm north of where I need to be, and bolt to the south. I immediately identify my correct river bend, and see St. Paul and recognize what happened. I am now at about 4500ft and start to descend to my planned 2000ft altitude.
Once I get there I head west, this time, remembering the wind and make it to McMinneville as planned (the green arrow).
So, while not a total crisis, it really did throw me. In our post-flight review we went over what happened, and I had a real chance to look over the map.
Wanna see something? That friggin island in the river I was over? It is on the map, just under the text, "178". Right under the "7". If I had only seen that on the map... this would have been a "Huh? Where am I? Oh, here. Ok, no biggie."
So, here is the full story. How I got in, how I got out, etc. (Mainly for you, Bob. :)
The planned flight plan is as shown here:
HIO is at the 12 O'Clock position, Mulino at 4 O'Clock, McMinneville at the 7 O'Clock. The part I'm interested in here is at the lower portion of the triangle. So, lets zoom a bit:
So, it all started as I was entering the airspace for Mulino airport (green arrow). There was a 9 knot wind blowing from 130º (black arrow).When you do your flight planning, you need to know about your airports. Their traffic patterns, runway lengths and directions, etc. Well, I did all that. I knew that Mulino had one runway strip, labeled Runway 14 and Runway 32. If you didn't know, they name the runways so that you can tell which direction they are facing. In this case, oriented to 140º and 320º, respectively.
So, anyway, I knew this. And since you want to land into the wind, whenever possible, the airports with a control tower will select the appropriate runway for you. In this case, there was no tower, so you have to rely on your knowledge, and the knowledge of the other people flying in the airport. The active runway is suppose to be Runway 14 with the wind coming from 130º. It just is. It also happens to be a right air traffic pattern runway. This means, that you are supposed to make right hand turns all the way to landing. Since I was coming in from the North West, I could have, technically come right in to the runway, almost straight on. But, that's not the cool thing to do. You are supposed to enter the downwind leg at 45º and make your right turns in. The image below shows a left pattern, but you get the idea. Just flip it so that you would land making right turns:
In my case, I would have to fly past the airport to the west, make a wide left turn so as to come in at 45º on the downwind leg and then enter the pattern. As a side note, while you always want to check the weather system broadcast in the area, you only trust what you can see. And luckily for me, there were a few wind indicators in the are for me to look at. Things like wind socks are always nice near an airport... but out west here, people tend to burn leaves and brush. And this day there were two fires going within about 1/2 mile of the runway. So, I was 100% sure of the wind. So, I broadcast my intention to "enter the right-downwind for Taxiway 14". We can land on taxiways or runways. It's cool of us not to take up runway space... and it is safer too.
Ok, enough background. So, I veer off to the right of runway 14 to make my wide left turn into the pattern when we see some dude in an airplane taking off on runway 32. The opposite direction on the runway. Taking off with a 9 knot tail wind. Not smart. Not to mention dangerous. So, I do a go around, and make a right hand turn to re-enter on the downwind. As I get about 270º in my turn, this dude that just took off cuts hard left and comes way too close to my flight path. Granted, I was at 800ft (as I'm suposed to be) and he was probably climbing past 1200, but still... not cool dude. So, I re-announce where I am, and what I'm doing. This wakes the airplane dude up, I guess, and he broadcast a quick "sorry about that, did not see you guys there". Huh? Really? I'm in a bright red helicopter with a giant rotating blade with my lights on... exactly where I said I would be. But, ok... fine. Stuff happens, and we were really not that close.
So, I do another go around. And we hear, on the radio another fixed winger come on the radio "
I turn off to the west and we just skip this approach at Mulino. In hindsight, we should have come on the radio with a "Mulino traffic, wind indicators clearly show that runway 14 should be in operation, not 32. Please check wind." But, we didn't. Totally one of those things you think of 5 minutes after you need it. But, all is well, and we're headed north west to Aurora with a bit of a tailwind.
A few minutes in to this leg Kristy says, "The FAA just called there is an accident in Aurora, divert to Lenhardt". Obviously the FAA did not call, she was just giving me a scenario to deal with. I didn't know where Lendhart was, so I had to look a little on the map. (To save you some time, it is the red arrow.)
So, I look it up on the map, estimate my course and direction and head to Lendhart. Eventually I see it off to the left, quite a ways away. I point it out to Kristy, and she gives me the OK to head to McMinneville. So, looking at the map, I head due west. I forgot to correct for wind... and this was my big flaw. I was heading NW. A lot more north than I expected, at least. I also think the wind had picked up a little, cause, as you will see, I was way off.
I was flying along to my next checkpoint, a significant bend in the river. What I was looking for is the blue circled area below. What I was flying over was the red circled area. I was way north of where I wanted to be. As I crossed the river, I saw this town... which, according to my plan, is not supposed to be there. As you can see, it was the town of Newberg. But, when I planned this out, I was not supposed to cross the river and see a town. So, wham, I'm lost.
The lost procedures are "the 5 C's". Calm, Climb, Circle, Calculate, Communicate. So, I take a deep breath, start climbing, and start doing a right hand circle. I start looking at the land, my map, etc. I find a significant feature on the ground below me, an island in the river. OK, great, there has to be an island on the map. So, I look, where I think I'm supposed to be... the blue circle. No island on the map. Shit. So, I conclude that either the island is not big enough to be on the map, or else I'm nowhere near this point on the map. First thing I do is look for an island in the river elsewhere on the map. And I don't see anything withing a reasonable flying distance. So, I'm now sure that this island I'm circling over, now at 3000ft, must not be big enough to show up.
So, screw this river, I think... now I'll look for a town. I should be seeing St. Paul to my south. (Remember, I think I'm in the blue, but am actually in the red circle). Nope, no St. Paul. Only this huge town to the north of the river. Could I be seeing Lafayette? Dayton? Where the F am I! Kristy is with me, of course, and being very calm. She knows exactly where we are... just wants me to struggle through. Which, is a great teaching tool, but it pissed me off. I'm now at 4000ft, circling like a moron, getting all twisted up.
Finally she speak up and says, "What are you using for your fix?" and I said, mention that I'm looking for the island in the river as well as the direction of the bend. "Are you looking for a 'C' to the east or a 'n' shaped bend to the south?". I believe I'm in the blue, so I'm looking for a 'C' to the east, but I'm actually in the red over a 'n' to the south.
This helps, obviously, and I suddenly realize I'm about 10nm north of where I need to be, and bolt to the south. I immediately identify my correct river bend, and see St. Paul and recognize what happened. I am now at about 4500ft and start to descend to my planned 2000ft altitude.
Once I get there I head west, this time, remembering the wind and make it to McMinneville as planned (the green arrow).
So, while not a total crisis, it really did throw me. In our post-flight review we went over what happened, and I had a real chance to look over the map.
Wanna see something? That friggin island in the river I was over? It is on the map, just under the text, "178". Right under the "7". If I had only seen that on the map... this would have been a "Huh? Where am I? Oh, here. Ok, no biggie."
Monday, March 10, 2008
Triangle of Stress (a.k.a. Triangle of Death)
Flight #: 049
CFI: Kristie H.
Aircraft: Robinson R22 Beta II
Aircraft ID: N2356T
Duration: 1.3hrs
Cumulative Time: 55.2hrs
WOAH, this was intense. The triangle of death consists of a cross country (XC) flight to three other airports. Portland-Mulino(4S6), Aurora State(KUAO), McMinnville (KMMV), and then back to Portland-Hillsboro (KHIO).
Round trip of about 70 nautical miles. The truth is, that is really not all that far, and when you are cooking along at 80 knots, things fly by pretty fast.So, before you even start a XC flight, you need to prepare a flight plan. There is a standard form, and as you can see, it is filled with gobs of information. The one posted here is just the template I use, as it will change depending on wind conditions. But, this gives you a good idea of what is needed.
In flight, you actually fold it and store it in your kneeboard. This way you only look at the details you need to see in flight. Which is mainly the checkpoints, the heading, segment time, altitudes, and communication frequencies.
Once you get this form filled out, you call 1-800-WX-BRIEF, which will connect you with your Flight Service Station. It is a service operated by Lockheed Martin that maintains information, weather data, and other details for a given flight. It is not Air Traffic Control, but a service to give you weather details on your flight plan and to maintain a track of where you should be, and where you might be if something goes wrong. Safety service, really.
So, you call FSS and for our area, they will connect you with McMinneville FSS. You ask for a briefer and then give them details about your flight. They will verify your data; checking to make sure you have the fuel to make it, look into weather along the path of flight, etc. They will also let you know of any special reports that you might be concerned with.
Once you complete this, you can consider your flight plan filed.
Then, it is off to the helicopter. You pre-flight and run-up as normal. Rather than requesting a pattern, you request a departure. In this case we're heading SE, so in this case, I requested a East departure to take off into the wind.
Climb out as usual, and check my first compass heading, and start my timer. As we transition out of KHIO airspace, we call up our buddies at McMinneville FSS to let them know we want to open our flight plan. It goes something like this:
Kristie: "McMinneville radio, this is 2356-Tango on 122.45."
FSS: "2356-Tango, McMinneville radio, say full call-sign."
K: "November-2356-Tango."
FSS: "Afternoon, 2356-Tango, What can we do for you today?"
K: "I'd like to open my flightplan."
FSS: "2356-Tango, what is your departure airport?"
K: "Hotel-India-Oscar."
FSS: "OK, got you here. What was your departure time?"
K: "Approximately 5 minutes ago."
FSS: "OK, so departure at 2122 zulu, confirm?"
K: "Correct."
FSS: "2356-Tango, your flight plan is now open. We do request pilot reports on FlightWatch at 122.0 if you have them. Please make sure to close your flight plan upon landing. Have a nice flight."
K: "Thanks. 2356-Tango".
As this point, they know where we are, where we are headed, how much fuel have, and when we are expected back.
Then the fun begins. It is all about communicating when flying. Make sure everyone knows where you are, and you know where everyone else is. Rather than explain every little detail; look at the first image above. I'm flying the triangle, clockwise. Every time I'm 10, 5, 3, 2, 1 nm from an airport (the blue or magenta circles, with or without the handles) I'm talking. I'm also checking weather for each of the airports I intend on landing. Basically, constantly. When you get to an airport, you need to let everyone know your plans. Where are you coming from? What altitude are you at right now? Ascending, descending? What direction are you traveling in? What are your plans? Landing, approach, etc, etc. Lots of communication.
Keep in mind, I'm hauling ass too... not time to dilly dally and check out the scenery. I'm checking speed, altitude, traffic around me. Am I over my checkpoints? How's the fuel?
Anyway, there is a lot of stuff going on here. Granted, I'm stuffing a lot of action into a small 70 nm flight here... but the point is that this is supposed to be intense. It is supposed to give you a bit of stomach acid so that you know how to deal with stuff when it comes up for real.
Anyway, we got back, landed, and closed the flight plan.
It was really cool, but really stressful.
I got to be honest, I was feeling pretty big after all my solos the past week. Big man, flying a helicopter. Now, I've got my ass out of the baby pool and into the deep sea.
So much for the feeling of superiority. This is intense!
View Larger Map
Saturday, March 1, 2008
The triangle of DEATH!
Weather has been a bit dicey in the past few days. Now that I've passed Stage 1, we took the opportunity to knock out the last Ground Lesson. I was WAY ahead on ground due to the moist Oregon winter. Might as well knock it all out.
Now that Stage 1 is out of the way it was time to start talking Cross Country flights. Cross Country flight just mean that we deal with more than just our local airports. There is a special circuit that CFIs have set up for your first cross country. Funny story behind that...
Kristie tells me were about to start off on solo and cross country flights. Since the ground training center at Hillsboro is rather small, you can easily overhear what is going on in each training cube. Here is a transcript:
Kind of reminded me of Finding Nemo and the initiation scene.
Anyway, I'm psyched for this. The "Triangle of Death" consists of flying to two airports before heading back to Hillsboro. It is a well known circuit and has some good distinct pilotage landmarks. Simply, you fly from Hillsboro(KHIO) to Mulino(4S9) to McMinnville (KMMV). About a 70 mile round trip covering some interesting land.
Part of the ground lesson was to start a flight plan. I had to get it into nice digital format: Hillsboro Flight Plan Document - Triangle of Death
Next week looks to have some hairy weather as well... so it may be a while before we get to make the run.
Now that Stage 1 is out of the way it was time to start talking Cross Country flights. Cross Country flight just mean that we deal with more than just our local airports. There is a special circuit that CFIs have set up for your first cross country. Funny story behind that...
Kristie tells me were about to start off on solo and cross country flights. Since the ground training center at Hillsboro is rather small, you can easily overhear what is going on in each training cube. Here is a transcript:
Kristie: "Were going to start off with [quietly] The Triangle of Happiness". Gareth happened to be right across the hallway.
Gareth: "What did you call it?!"
Kristie: "Nothing, don't bother us."
Gareth: "Did you say, 'Happiness'?"
Kristie: "[Embarrassed] Yes."
Gareth: "It's not called the 'Triangle of Happiness'... It is called..."
CFIs in hearing distance:
"The Triangle of Death!"
Kind of reminded me of Finding Nemo and the initiation scene.
Anyway, I'm psyched for this. The "Triangle of Death" consists of flying to two airports before heading back to Hillsboro. It is a well known circuit and has some good distinct pilotage landmarks. Simply, you fly from Hillsboro(KHIO) to Mulino(4S9) to McMinnville (KMMV). About a 70 mile round trip covering some interesting land.
Part of the ground lesson was to start a flight plan. I had to get it into nice digital format: Hillsboro Flight Plan Document - Triangle of Death
Next week looks to have some hairy weather as well... so it may be a while before we get to make the run.
Subscribe to:
Posts (Atom)