Posts Tagged ‘airplane’

The Joys of Buzzing Market Street in Your Aging Cessna 310 Twin – What’s the “Minimum Safe Altitude” Over SF?

Wednesday, February 27th, 2013

This is a Cessna 310, or something similar, just after it buzzed the Financial at well under Minimum Safe Altitude, which in this case is 1000-something feet above ground level.

Escaping to the northeast:

Click to expand

Now, do I have your tail number? No I don’t. So you win this round, Flyboy.

Regardless, I cry foul.

Until next time…

(And try to not kill yourself or your  passengers or any ground-dwellers before then.)

 

 

Know Your Northern California Spy Plane Nose Art: Beale AFB U2 “Dragon Lady” = Santa’s Sleigh

Tuesday, December 11th, 2012

See?

Click to expand

Fly It Like You Stole It – Sailing High Over the Western A

Wednesday, October 24th, 2012

My, what a long contrail you have…

Click to expand

So This Is What a Temperature Inversion Layer Looks Like – Welcome to Los Angeles, Cough Cough

Friday, August 17th, 2012

Here’s the View from Seat 6AAugust 2012 Over a Trapped Layer of LA Smog:

Click to expand

Wow.

I want to live in los angeles
Not the one in los angeles
No, not the one in south california
The got one in south patagonia

Wow: Seeing San Francisco From Above the Mission District Through “Omni-Vision” – Rear Window, Cessna Skyhawk

Friday, August 10th, 2012

Hey man, nice shot.

Via singlespeeder2007:

Click to expand

Viewing notes:

Hey, can you guess which street in San Francisco was remade to be a firebreak, you know, around 1906? Sure you can. Just look at the photo. You see, it, unlike the useless, quarter-mile long, Octavia Boulevard “Livable Streets” experiment, is wide for a reason. 

Omni-Vision – This referred to the rear windows on some Cessna singles, starting with the 182 and 210 in 1962, the 172 in 1963 and the 150 in 1964. The term was intended to make the pilot feel visibility was improved on the notably poor-visibility Cessna line. The introduction of the rear window caused in most models a loss of cruise speed due to the extra drag, while not adding any useful visibility

National Transportation Safety Board Holds Tesla Automotive Employee Responsible for Fatal Air Crash in Palo Alto

Monday, November 28th, 2011

(As always, If You Assume That Any Given Plane Crash is Due to Pilot Error, You’ll Probably Be Right.)

Here’s an article about the new NTSB report.

Does it make sense to commute to Los Angeles for work, assuming you had a pilot’s license and an airplane? I don’t know.

Does it make sense to listen to the advice of your air traffic controller concerning the advisability of taking off into heavy fog, even if you don’t have to? Yes it does.

Is there a reason why pilots are told to turn over the Bay after takeoff? Yes there is.

Oh well.

Here’s what people down Palo Alto Way are saying.

And here‘s the “chilling recording” from a SpotShotter tower. (It’s about what you’d expect, with crashing noises and the yelling of the day care center kids who saw the crash.)

The former N5225J, a Cessna 310R with relatively new, perfectly-fine-at-the-time engines: 

(I’ll tell you, I don’t know why our federal government subsidizes Tesla Automotive (and for that matter, General Monkeybusiness in Detroit). Was Tesla paying for the avgas that this Cessna was burning? Does Tesla reimburse CEO Elon Musk for the jet fuel that he burns as he joyrides around the world, as is his wont? I think Tesla used to, but I don’t know about these days. You know, for an electric car company what’s produced not a whole bunch of electric cars, Tesla seems to burn up a lot of petroleum…)

Anyway, here’s the summary – the whole thing you’ll find after the jump.

NTSB Identification: WPR10FA136

14 CFR Part 91: General Aviation

Accident occurred Wednesday, February 17, 2010 in Palo Alto, CA

Probable Cause Approval Date: 11/22/2011

Aircraft: CESSNA 310R, registration: N5225J

Injuries: 3 Fatal.

The pilot departed the airport in near-zero visibility instrument meteorological conditions, and shortly after takeoff, struck a power pole and power lines before impacting terrain. Review of recorded air traffic control tower (ATCT) transmissions revealed that the pilot was initially given his instrument flight rules (IFR) clearance to turn right to a heading of 060 degrees and climb to 3,000 feet. Shortly after verifying his IFR clearance, the pilot received his IFR release from the ATCT controller and was informed that the runway was not visible to the controller. The controller further informed the pilot that takeoff was at his own risk. Shortly after, the controller notified the pilot that he had two minutes for his IFR release, before it expired. The pilot stated that he did not hear a “cleared for takeoff” instruction from the controller. The controller responded that he could not clear the pilot for takeoff, due to not having the runway environment in sight and that “the release is all yours and it’s at your own risk sir.” The pilot acknowledged the transmission and proceeded to take off. One witness, who was adjacent to the accident site, reported that she observed an airplane “suddenly appear from the fog” left of her position. The witness stated that she continued to watch the airplane fly in a level or slightly nose up attitude until it impacted power lines.

Accident site evidence was indicative of a level impact with a power pole about 50 feet above ground level (agl) and at a high airspeed. All major structural components of the airplane were located within the wreckage debris path. Examination of the airframe, engines and propellers disclosed no evidence of any preimpact mechanical anomaly. Weather conditions reported five minutes prior to the accident were wind variable at 5 knots, visibility 1/8th mile, fog, and vertical visibility of 100 feet agl. Weather conditions recorded by the ATCT 11 minutes after the time of the accident were visibility 1/16th mile, fog, and a vertical visibility of 100 feet agl.

Local law enforcement provided recordings from a sound recording system, which captured the accident sequence. The recordings were coupled with airport surveillance radar to interpolate a flightpath for the airplane. The interpolated flightpath indicated an approximate 45-degree left turn shortly after departure to the area of initial impact with the power pole and power lines. A sound spectrum study determined both engines were operating near full power.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot’s failure follow the standard instrument departure as instructed, and his failure to attain a sufficient altitude to maintain clearance from power lines during takeoff in instrument meteorological conditions.”

(more…)

Know Your Two-Seat, Russian, Yakovlev Yak-52 Acrobatic-Training Aircraft Above San Francisco

Wednesday, September 28th, 2011

Remember that Yak-50 what used to buzz about the bay area? Good times. (See below for some shots taken from the East Peak of Mt. Tam.)

Well this is better, this one’s a Yak-52 (Як-52). Hurray!

(It probably killed fewer pilots per hour than the single-seat Yak-50, so that’s nice.)

As seen from Land’s End:

Click to expand

(In Soviet Russia, plane kill you!)

What kind of crazy airplanes will Mother Russia send over next?

“This Russian-made Yak-50 acrobatic airplane used to be seen all over the skies of the San Francisco Bay Area – buzzing Mount Tam in Marin County, checking out anti-abortion rallies along San Francisco’s waterfront, that kind of thing.

But here’s your take-away, babe: These things had a working life of just 50 hours back in Mother Russia, as the stress of all them 9G loop de loops and whatnot led to bad things, such as “main spar collapse.” Ouch.

Anyway, looks like fun:

Click to expand

Canon 1D Mark II with 300mm 2.8 IS I and 2x extender – ISO 400 and lots of digital zoom:

Happy trails.”

The Hollywood Hills, as Seen from the Trip Down to LAX

Wednesday, September 7th, 2011

Here they are.

Do you see the big sign?

Click to expand

People, Turn Off Your iPods and Whatnot When You’re Below 10,000 Feet the Way They Tell You – Here’s Why

Thursday, March 10th, 2011

Now it’s sort remarkable how no passenger has died the past decade in an Airbus or Boeing jetliner that either took off or landed in the United States. Of course there was the 9/11 and shortly after that at the end of 2001 there was American Airlines Flight 587, but since then, nothing. That’s a pretty good record, non?

But you people, you don’t listen when they tell you to turn off your portable electronic devices during critical phases of flight. And then stuff like this happens.

Just saying, bro-ham.

Ah the daily Lufthansa flight from Frankfort, Germany. This happens to be an aging Boeing 747-400, but in a few months it will get replaced by a superjumbo A380.* Can you see someone iPodding or texting up there? I can:

Click to expand

*No, contrary to what the Mayor’s Office tells you, the A380 doesn’t use less fuel than legacy aircraft. And the version that’ll soon be coming to SFO each and every day has wings that are too big for its body, and it’s overweight, and blah blah blah. But oh well.

SFO Departures on Those Rare Days with Midwestern Skies: Hang a Left at the Moon and Your Next Stop is LAX

Friday, November 19th, 2010

When we get those crazy days with Midwestern skies and offshore breezes, SFO traffic control makes your pilot take off to the northeast over the bay instead of to the northwest over “South” San Francisco. That means that airspace over San Francisco proper temporarily sees a lot more traffic.

Like yesterday.

As seen from Civic Center:

Click to expand