More GoPro Camera Tests, More Aerial Photos and Videos

Another chapter in my never ending saga: any excuse to fly.

Early this week, it rained.

That might not seem like a big deal to most folks, but it rains very seldom in Arizona. In fact, I hadn’t experienced a good rainstorm since my drive back from Washington state in October.

This week, it was cold and rainy for two days in a row. With rain comes three things:

  • Clouds, which make our normally plain blue sky more interesting and give it depth.
  • Cleansing, by which I mean that the dust is washed off the desert rocks and plants, making their colors more vibrant.
  • New growth in the desert, which makes everything look just a tiny bit greener than it otherwise would.

You need to be a desert dweller to really appreciate these things.

There’s nothing I like more than to go flying over the desert right after a good rainstorm. So on Wednesday, as the storm clouds moved north and blue sky started to appear again, I loaded up my GoPro cameras and mounts, hopped in the car, and drove up to Deer Valley Airport, where my helicopter is living part-time this season. When I arrived just before 9 AM, my helicopter was sitting out on the pavement, ready for me to preflight, set up my cameras, and go.

The Camera Setup

I took my time about setting up the three GoPros. I have three different models and I use each one for a different purpose.

  • GoPro HD Hero2 Professional – With its sound-in port and better lens and recording capabilities, I normally mount it on the helicopter’s nose as the “nosecam” and connect it to an audio-out port I had put into the helicopter a few years back. It captures not only intercom communications, but all radio communications. Basically, anything I hear in my headset is also sent out through that port to my GoPro. Here’s an example of an image from the video on this camera, shot at 720p:
    Bartlett Dam Nosecam
  • GoPro Hero HD Original – I mount this between the helicopter’s two back seats, inverted, to capture a wide-angle view of what’s going on inside the helicopter and beyond. This “cockpitcam” view works fine with passengers, but it doesn’t give a close-up view of the instrument panel. For that, I need to mount the camera forward, on the bar between the two front seats. Here’s a view from the camera as I had it mounted Wednesday, also shot at 720p video:
    Back Seat View
  • GoPro Hero 960 – Because I haven’t been exactly thrilled with the 1080p video coming out of my original GoPro HD Hero, when I decided to invest in a second one, I went with the cheaper model, which can’t shoot 1080p video. Instead, it shoots up to 1280×960. I like the widescreen format, so I shoot 1280×720. I saved about $100. On Wednesday, I used a new skid mount and set it up to snap a 2592 × 1944 still image every 10 seconds. (In the 20-20 vision of hindsight, I should have set it up for every 2 seconds; 6 shots per minute isn’t quite enough when you’re cruising at 100 miles per hour.) Here’s a sample image from that “skidcam”:
    Bartlett Dam

So to summarize: I set up the helicopter as a camera mount for three different cameras: 2 shooting video and 1 shooting stills.

The Flight and Some Photos

I turned on all the cameras, climbed into the cockpit, and started up. Five minutes later, I was overflying Deer Valley Airport at 500 feet AGL, northbound. Here’s a nice shot of the airport from the nosecam:

Deer Valley Airport, Northbound

The beauty of all this was that with this setup, I’m able to capture images from three cameras without having to even think about any of them. Absolutely no distraction for me, allowing me to keep my full attention on my primary duties as a pilot: aviate, navigate, and communicate.

The flight was not quite what I had in mind. I was hoping to overfly Lake Pleasant and get all the way to Wickenburg. But as I neared Lake Pleasant, I saw low clouds over the lake. There was mountain obscuration to the northwest — which means the clouds were pretty darn low, since those mountains aren’t exactly lofty peaks. Here’s a nose cam image of the marina at Lake Pleasant near the dam; you can see the low clouds at the north end of the lake:

Marina at Lake Pleasant

I wasn’t very interested in getting images and video shot in overcast conditions. So I decided to head east, where the sky was clearer and sunlight was filtering through to the desert floor.

There was a balloon flying southeast of Lake Pleasant and I tried to get some shots of it with the skidcam. Trouble is, the GoPro’s very wide angle lens exaggerates the distances. If I wanted a good shot of the balloon where it looked close, I’d have to get much closer to the balloon. While I think I could have gotten closer safely, I didn’t want to give the balloon operator or his passengers heart failure so I stayed clear. This is the best I could get; again, a shot every 2 seconds would have given me more to choose from.

Hot Air Balloon

As I flew east, the two front-facing cameras were pointing toward but not exactly into the sun. GoPro cameras get their best images when the sun is at an angle of at least 60 degrees from the lens. According to the LightTrac app on my iPhone, at about 9:45 AM the sun was at about 140 degrees. I was flying at about 90°, so the sun was at 50° angle to the front-facing cameras. At the same time, it was at a 40° angle to the skidcam, which was facing almost due south. (Obviously, I didn’t look up the angles while flying.) As a result, the images from this leg of my flight were pretty disappointing. Here’s an example from the cockpitcam as I flew over the intersection of I-17 and Carefree Highway:

I-17 and Carefree Highway

I flew all the way out to the Verde River and then headed up the river as far as Bartlett Dam. The two photos near the beginning of this post shot nosecam and skidcam views. Since more gray skies and low clouds covered Bartlett Lake, I turned around and headed south. The cockpitcam shot near the beginning of this post shows my view as I headed approximately southwest. After a tiny bit of shallow canyon flying (see nosecam photo below), I headed toward Scottsdale where sun, low clouds, and rocky outcroppings made for interesting views.

Canyon Near Verde River

I got a nice shot of Pinnacle Peak from the skidcam at several altitudes for use in a book project I’m working on.

Pinacle Peak

I also got nosecam and cockpitcam footage as I approached the peak. Interesting to see the difference between these two views, shot at about the same time.

Approaching Pinnacle Peak

Approaching Pinnacle Peak

By that point, I’d been in the air for about an hour and thought I had enough footage to test my setup thoroughly. I headed back to Deer Valley. The one mistake I made was that I flew along side a power line, with the power line on my right — right in the view for my skidcam. This was very unfortunate because the camera was facing north at this point and could have captured a lot of nice footage. Instead, all the footage features the damn wires.

Wires in my Photos

I guess that proves that I wasn’t really thinking much about the cameras.

And for those who are interested in such things, this is the track log of where I flew, as recorded on my iPad.

Track Log

The End Result

In all, I got just over 300 photographs and 2 hours of video — an hour from each camera. Quite a bit of it is useable and will likely appear in edited video content I produce in the future.

I plan to try shooting video from the skidcam. I could see it from my window and checked it a few times in flight to see how much it was vibrating — it didn’t seem to be vibrating much at all. Of course, you can never tell until you shoot the video and see the results. So that’ll be my next test, probably tomorrow.

A Final Note about the Camera Setup

I took photos of all my cameras as they were mounted before beginning the flight. I hesitate, however, to share them or provide detailed information. Although I know many pilots who regularly mount cameras on the outside of their aircraft, it’s one thing to talk about it and another to document it with photos for the world to see. I’m very confident in two things:

  • Any camera I mount on the outside of my aircraft will not fall off. I use several safeguarding measures to ensure this. I am positive I will not lose a camera.
  • None of the mounting locations affects the aerodynamics of my aircraft. In other words, it flies just as well with the cameras attached as it does without them.

These are the only things that should concern a pilot or anyone overseeing that pilot’s activities.

Comments? Questions?

I welcome your comments, questions, and suggestions. Post them here.

Amazon’s Bribe to Publishers: KDP Select and the $6 Million Fund

And why I’m giving it a try.

I published my first real ebook back in the end of October: Making Movies: A Guide for Serious Amateurs. I built the book in InDesign, spun off a color print-on-demand version through MagCloud, and then painstakingly prepared ebook formats for the iBookstore, Amazon Kindle, and Barnes & Nobel Nook. Within a week, it was widely available and actually began to sell.

The Kindle Owners’ Lending Library

Not long afterwards, Amazon.com sent a chill through the publishing industry by announcing that Kindle owners who were also Amazon Prime subscribers would be able to borrow books — for free — from Amazon.com. The program is called Kindle Owners’ Lending Library and its an obvious ploy by Amazon.com to make its Kindle hardware more attractive to readers. After all, you must have a Kindle — the actual device and not a Kindle app on an iPad or computer — to borrow the books for free. So for those readers who don’t need all the features of a real tablet computer, this program makes a Kindle a bit more attractive.

I immediately questioned one of my publishers in its private Facebook group:

As an author, I’m wondering how Peachpit’s participation in this program (if they do participate) will impact royalties.

After all, I don’t earn royalties from borrowed book; I only earn royalties on purchased books. Apparently, I wasn’t the only one thinking about this. The Mac Observer published a piece titled “Amazon’s Lending Library Raises Publisher & Author Hackles” that explored the program and responses to it in some depth.

In the Facebook group, the publisher’s response was quick and to the point:

[Publisher Name] is not participating.

I found this reassuring. The reason: If readers knew they could get my books for free, they might stop buying them. If they stopped buying them, I would not be able to earn a living. Pretty simple, no?

So I saw the program as a threat to my livelihood and was glad to hear that my biggest publisher was not going to participate.

Fast Forward to Last Week

On Thursday, I got an email message from the Kindle Direct Publishing service. That’s the service publishers use to get their ebooks for sale on Amazon.com. It started like this:

We’re excited to introduce KDP Select — a new option dedicated to KDP authors and publishers worldwide, featuring a fund of $500,000 in December 2011 and at least $6 million in total for 2012! KDP Select gives you a new way to earn royalties, reach a broader audience, and use a new set of promotional tools.

It went on to say that if I opted to include my book in the Kindle Owners’ Lending Library, I could get a cut of a monthly $500,000 fund based upon the total number of times my book was borrowed. Of course, Kindle owners would be attracted to these books because they were free to borrow. And now I could get a royalty payment on a borrowed book.

It seems like win-win-win:

  • Amazon wins because it gets more books in the Kindle Owners’ Lending Library, thus enhancing the value of the Kindle and Amazon Prime programs.
  • Kindle Owners with Amazon Prime memberships win because there are more books available to borrow for free.
  • Authors/Publishers win because they actually get paid when people read their work.

I thought long and hard about why I might not want to give this a try with Making Movies.

The only drawback for me as a publisher is that I had to give Amazon.com the exclusive right to sell/loan my ebook for at least three months. I could not distribute an ebook version of the title anywhere else — not on Apple’s iBookstore, not on Barnes & Nobel, not on MagCloud, and not even on my own website or blog.

I looked at the sales figures from all the places my book appeared. I’d already sold more copies with Amazon.com than with all of the other retailers combined.

It was a pretty easy decision.

So today I enrolled Making Movies in KDP Select.

The way I see it, three months is not a very long time. If I fail to bring in enough royalty money during that period to continue allowing Amazon to have an exclusive on my ebook, I’ll drop out of the program.

And I know of at least one other author who has enrolled his title: Andrew Dambe with his novel Soleá. (I started reading it; it’s a neat book.)

It’s worth a try, right?

Move Over, Reindeer! Santa’s Got a New Sled

I take the honorable Mr. Claus by helicopter to meet his adoring fans.

Yesterday, I had an unusual gig: I had to fly Santa Claus for an appearance at the Deer Valley Airport Restaurant in north Phoenix.

Santa asked me to take the door off. He has a thing about waving to his fans as the helicopter approaches. It also makes it easier for him to get out.

Let’s face it: Santa is a big guy. I bet he eats like it’s Christmas all year ’round at his place. But surprisingly, those inches didn’t translate to pounds. He weighed in at 180; it was almost as if that big belly of his was as light as a feather pillow.

Anyway, here are two shots from the flight. My husband was on the restaurant’s rooftop patio and recorded our approach and landing.

Santa's New Sled

Santa's Departure

Snowballs from My Oven

Another recipe from my annual baking extravaganza.

Every year, I bake cookies for my favorite clients. They always include my famous helicopter sugar cookies and my favorite oatmeal chocolate chip cookies. And sometimes they include so-called “magic cookie bars” or brownies.

Snowballs from my OvenThis year, they include “Snowballs.” This is a small spherical cookie made primarily of butter, flour, and finely chopped nuts, dusted with powdered sugar. Tasty without being too sweet.

Here’s the recipe for four dozen. I doubled it and got just under 8 dozen.

Ingredients:

  • 1 cup butter or margarine, softened. I used half butter and half margarine.
  • 1/2 cup powdered sugar.
  • 1 teaspoon vanilla.
  • 2-1/4 cups all-purpose flour. I use unbleached.
  • 1/4 teaspoon salt.
  • 3/4 cup finely chopped nuts. I used walnuts which I chopped almost to a coarse powder in my food processor.
  • More powdered sugar.

Instructions:

  1. Heat oven to 400°F.
  2. Beat butter, measured powdered sugar, and vanilla in a large bowl with an electric mixer on medium speed.
  3. Stir in flour and salt. I did this in the mixer on lowest speed.
  4. Stir in nuts. Again, I did it in the mixer. The dough ends up being rather dry and does not cling to the side of the mixer bowl.
  5. Shape dough into one-inch balls.
  6. Snowballs before BakingPlace balls about 2 inches apart on an ungreased cookie sheet. Because these don’t flatten out, you can get quite a few on a standard sized baking sheet or jelly roll pan. Although my first sheet had only a dozen (see photo), I was able to get two dozen on subsequent baking sheets.
  7. Baked SnowballsBake for 8 to 10 minutes or until set but not brown. I judged that they were done when the tops began to crack ever so slightly.
  8. Snowballs Dusted with SugarImmediately remove from cookie sheet and roll in powdered sugar. Now although I tried this, I soon discovered that this was a very messy way to go about coating them with sugar. So instead, I put them on a wire rack with some newspaper (okay, it was Trade-a-Plane) under it and used a tea strainer to sift powdered sugar over them.
  9. Cool completely on wire rack.
  10. Roll in powdered sugar again. Now although this is part of the recipe, I didn’t do it. Too messy!

If you have two baking sheets, I recommend using them both. It took me about 8-10 minutes just to roll up the next batch of cookies, so I was able to have a sheet in the oven at all times. This really saves energy when you’re running an oven at 400°F.

If you try this recipe, please let me know what you think. I love them.

Required Reading for Helicopter Tour Pilots

Two accident reports that clearly demonstrate how “hot dogging” can get you — and your passengers — dead.

November 25, 2013 Update:

The NTSB’s probable cause report for this accident is now available. The pilot was not at fault in this particular accident — it was a maintenance issue. As a pilot, I’m glad that the pilot’s name was cleared of fault but, at the same time, I’m concerned that maintenance shortcomings caused five deaths. The pilot was flying a ticking time bomb and it went off. There was nothing he could do to prevent the crash. And that scares me.

While the points presented in this blog post clearly do not apply to the Boulder City crash mentioned here, they are still important reading material for all pilots. Learn from other people’s mistakes.

On Wednesday, a Sundance Helicopters AS350 with a pilot and four passengers on board, crashed in the mountains near Boulder City, NV. It was on a “twilight tour” of the Hoover Dam and Lake Mead.

At this point, there’s no speculation about how the accident occurred. But, as usual, the media is dragging all the dirt they can out into the limelight to sensationalize the event and give people potential places to point blaming fingers.

One of the things the media has brought up is another Sundance Helicopters crash that occurred back in September 2003. I was unfamiliar with this crash — it must have occurred before my regular reading of NTSB accident reports began. Unsure whether I was confusing it with another crash, I looked it up today. But no, this was yet another instance of stupid pilot tricks becoming deadly pilot tricks.

I thought it was worth reviewing this case and another I’ve covered in the past and urge pilots to read both of the final reports carefully to see how reckless flying can kill. What’s interesting to me is how similar these two cases are — heck, they even took place within 30 miles of each other.

LAX01MA272: AS350, August 10, 2001, Meadview, AZ

I covered this accident briefly in Part 5 of my “So You Want to Be a Helicopter Pilot” series. Here’s the NTSB summary:

On August 10, 2001, about 1428 mountain standard time, a Eurocopter AS350-B2 helicopter, N169PA, operating as Papillon 34, collided with terrain during an uncontrolled descent about 4 miles east of Meadview, Arizona. The helicopter was operated by Papillon Airways, Inc., as an air tour flight under Code of Federal Regulations 14 (CFR) Part 135. The helicopter was destroyed by impact forces and a postcrash fire. The pilot and five passengers were killed, and the remaining passenger sustained serious injuries. The flight originated from the company terminal at the McCarran International Airport (LAS), Las Vegas, Nevada, about 1245 as a tour of the west Grand Canyon area with a planned stop at a landing site in Quartermaster Canyon. The helicopter departed the landing site about 1400 and stopped at a company fueling facility at the Grand Canyon West Airport (GCW). The helicopter departed the fueling facility at 1420 and was en route to LAS when the accident occurred. Visual meteorological conditions prevailed, and a visual flight rules flight plan was filed.

The pilot had a reasonable amount of experience with nearly 3,000 hours of flight time, all of which was in helicopters. He had CFI and instrument ratings.

The pilot, however, also had a reputation for hot-dogging. From the NTSB report‘s interview with previous passengers:

According to the passengers, once the tour started, the pilot was talking all the time. He was very informative, and they felt he knew his history and geography very well. They went over the Hoover Dam and Lake Mead. About 20 minutes into the flight, the pilot turned his head toward the back and was talking to the passengers as the helicopter flew toward a cliff. The people in the back were trying to get the pilot’s attention and point out that he was flying toward a cliff, but he pretended he did not understand what they were saying, as if this was all being done on purpose. All this time, the pilot was turned around and talking to the passengers in the back seat, while the passengers were all pointing up trying to get him to climb. One witness said she finally picked up the microphone and said, “they are really scared…turn around and pull up the helicopter,” and he did. She could not estimate how far they were from the cliff when the pilot terminated the maneuver.

One of the passengers stated that there were particularly exciting episodes during the tour that were frightening to some of the others. As part of the tour, they flew over a site that was used in the commercial motion picture film Thelma and Louise, and the pilot pointed out the cliff. The pilot stopped for fuel before he landed in the canyon for the picnic lunch. After lunch, no more stops were made. During the return to LAS, the pilot asked if they wanted to know what it was like to drive a car off of a cliff. She stated that they all said “no” to this question; however, he proceeded to fly very fast toward the edge of the cliff and then dove the helicopter as it passed the edge. The passenger reported that it was “frightening and thrilling at the same time but it scared the others to death.”

Both of these incidents — heading directly for a cliff and then diving like Thema and Louise over a cliff — were confirmed in a video tape provided by the passenger.

Crash Site
I don’t think the pilot expected to end up like Thema and Louise, too.

Evidence at the crash site indicated that not only was the helicopter’s engine producing power at the time of impact, but the collective was full up. The debris field was compact, indicating very little forward movement when the helicopter hit the ground. There was no evidence of any mechanical failure immediately before the crash. The NTSB ruled out many accident scenarios based on mechanical malfunctions before concluding:

In the absence of any evidence to indicate a preimpact mechanical malfunction, and given the density altitude, helicopter performance considerations, and virtually all of the signatures evident at the IPI and in the wreckage, the investigation revealed that a probable scenario involves the pilot’s decision to maneuver the helicopter in a flight regime, and in a high density altitude environment, which significantly decreased the helicopter’s performance capability, resulting in a high rate of descent from which the pilot was unable to recover prior to ground impact. Additionally, although no evidence was found to indicate that the pilot had intended on performing a hazardous maneuver, the high rate of descent occurred in proximity to precipitous terrain, which effectively limited remedial options available.

In other words, he most likely performed his Thelma and Louise maneuver, dove off the cliff, and because of high density altitude, was unable to arrest the decent rate before hitting the ground.

LAX03MA292: AS350, September 20, 2003, Grand Canyon West, AZ

This case is a lot worse. I’ll let the NTSB describe what happened briefly:

On September 20, 2003, about 1238 mountain standard time, an Aerospatiale AS350BA helicopter, N270SH, operated by Sundance Helicopters, Inc., crashed into a canyon wall while maneuvering through Descent Canyon, about 1.5 nautical miles east of Grand Canyon West Airport (1G4) in Arizona. The pilot and all six passengers on board were killed, and the helicopter was destroyed by impact forces and postcrash fire. The air tour sightseeing flight was operated under the provisions of 14 Code of Federal Regulations Part 135. Visual meteorological conditions prevailed for the flight, which was operated under visual flight rules on a company flight plan. The helicopter was transporting passengers from a helipad at 1G4 (helipad elevation 4,775 feet mean sea level [msl]) near the upper rim of the Grand Canyon to a helipad designated “the Beach” (elevation 1,300 msl) located next to the Colorado River at the floor of the Grand Canyon.

You need to read the NTSB’s full report to fully understand what happened here. You can download it as a PDF (recommended) or read it online.

The pilot was experienced. He was 44 years old with an ATP certificate for multiengine airplanes and for helicopters. He had CFI and instrument ratings for a variety of aircraft. He’d logged nearly 8,000 hours of flight time, nearly 7,000 of which was in helicopters. He had a clean record with the FAA.

But the pilot had also earned the nickname “Kamikaze” because of the way he flew. (And you can bet your ass that the media is having a field day with that in its coverage of Wednesday’s accident.)

99° Bank Angle
55° Pitch Angle
Two images from the NTSB report, calculating angles based on photographs and videos shot during other flights.

With a great deal of supporting evidence from the pilot’s previous passengers that same day and earlier, as well as photographs taken during flights with the pilot, the NTSB concluded that the pilot had a history of risk-taking behavior. Photographic evidence showed him flying at bank angles exceeding 90° with nose-down attitudes exceeding 50°. It’s estimated that he typically reached speeds up to 140 knots and rates of descent of 2,000 feet per minute.

With passengers on board.

For comparison’s sake, Sundance policy limited bank angles to 30° and pitch angles to 10° — both of which are very reasonable. Other pilots typically flew that portion of the flight at 110 to 120 knots, descending at 1,000 feet per minute.

Yet the report cites one passenger story after another of the pilot diving into the canyon and flying close to canyon walls. One former Sundance employee who had flown with him stated he “flew very close to the canyon wall” and “banked off one wall and then turned the other way, almost upside down.” One passenger claimed that his friend’s wife was screaming throughout the entire descent.

Sundance received at least two formal complaints about the pilot. There’s no evidence that anything was done about the first. The pilot was suspended for a week without pay after the second, but since Sundance was short of pilots, the penalty was never enforced and the pilot continued working with pay.

It should come as no real surprise that the pilot ran out of luck. According to the NTSB, on that September day:

The helicopter’s main rotor blade struck a near-vertical canyon wall in flight. The resulting damage to the main rotor system likely rendered the helicopter uncontrollable, and the helicopter subsequently impacted a canyon wall ledge.

There was a fireball when the helicopter exploded on impact. There wasn’t much wreckage. You can see for yourself; there are photos in the report. I wouldn’t even know it was a helicopter if it weren’t for the arrows pointing out parts.

Probable cause placed the blame on the pilot, as well as Sundance and the FAA:

The National Transportation Safety Board determines that the probable cause of this accident was the pilot’s disregard of safe flying procedures and misjudgment of the helicopter’s proximity to terrain, which resulted in an in-flight collision with a canyon wall. Contributing to the accident was the failure of Sundance Helicopters and the Federal Aviation Administration to provide adequate surveillance of Sundance’s air tour operations in Descent Canyon.

Disregard of safe flying procedures. That’s a bit of an understatement, no?

What We Can Take from This

If you don’t get the message I’m trying to convey here, you probably shouldn’t be flying anything — let alone passengers for hire in a helicopter.

It’s a fact: many of us fly a little nutty once in a while. Maybe low and fast over flat desert terrain. Or maybe threading our way though empty canyons at high speed. Or performing some other maneuver that takes all your attention and can easily turn into a disaster.

But when does “a little nutty” turn into pushing the aircraft beyond company or manufacturer limitations?

And who in their right mind would fly so dangerously with passengers on board?

You?

I hope not.

The point is that flying like a stunt pilot can get you killed. And if there are passengers on board, you’ll kill them, too.

Is that something you want to be remembered for? Do you want to be the subject of another pilot’s blog post about flying like an asshole with passengers on board? Do you want a derogatory nickname like “Kamikaze” brought up by the press eight years after your death when another pilot who works for your company is killed in a crash with his passengers?

How do you think the “Kamikaze” pilot’s family feels about his accident being brought up again? And again?

Think about why these pilots flew the way they did. Were they showing off? Or trying to get a rise out of their passengers?

In both instances, passengers made it clear — verbally, during the flight — that they didn’t want the pilot to fly the way he was. Think about the people pointing to a cliff face or the woman screaming throughout the descent. Why did these pilots treat their passengers with such disrespect? Scare them for no reason? Put their lives in danger? Was this fun for them? When is fun an excuse to risk other people’s lives?

Do you do this? If so, why? When will you stop? When your crash makes a big fireball like the ones in these stories?

Do you understand what I’m trying to say?

Read these accident reports. Two pilots are responsible for the deaths of eleven people with a twelfth person permanently disfigured.

Isn’t that enough to convince you not to fly like an asshole?

I only hope that Wednesday’s accident report isn’t another example for this blog post.

And my thoughts go out to the families of the victims of this stupidity.