Welcome to the Hardcore Husky Forums. Folks who are well-known in Cyberland and not that dumb.
Your favorite conifer of the Western US?
Comments
-
Western Red Cedar
My daughters (Camry and Corolla) approve this message…1to392831weretaken said:
So only for biggus dickus, secure in their manhood, logical, use the best tool for the job manly men? You make a good point!YellowSnow said:
The Doug Fir is the Toyota Sienna of conifers @1to392831weretaken1to392831weretaken said:#2 grade. Good for framing.
CSB Tim: Everyone assumes my daughter's name is "Sienna" like the minivan and not "Siena" like the city in Italy after which she was named. It was only dumb luck that her hair is the exact color of the buildings there, so I could understand not seeing the connection, but, come on... I like minivans, but that much?
-
Ponderosa PineYellowSnow said:
I don't think they have a Ponderosa at the OR State Capital either. To damn moist for them in Salem.PurpleThrobber said:https://www.spokesman.com/stories/2023/may/08/ponderosa-pines-and-other-trees-of-eastern-washing/
The fags (Hi Bob Huggins) in Olympia just yesterday recognized that, in fact, there are trees in the 509 area code.
TTTTT, I know.
WAR PONDEROSA!!
WOOD!
Alas, my Ponderosas are bigger and better than yours (more sunshine) and the MILFS are richer and hotter.
The Gosser Ranch Milfs had a good chuckle at that.
-
Douglas FirLots of good choices, but for me, nothing tops an old growth Douglas Fir. They can be hard to find in my neighborhood, just like giant red cedars, unless you walk steep stream valleys where the pioneers couldn't get to them. The bark, the straight trunk, and the height (though most have lost their tops there are 250'+ firs out here. The Doug fir can outgrow pretty much anything in terms of height.
The giant redwoods are undeniably cool. Quite a few of them grow around here (not native) and I'm amazed at how many people don't know about the wrestling mat-like sponginess the bark has. You can punch them pain free and for some dumb reason I always like to show people that That's good wood too. -
Sitka SprucePartial to the Spruce. Little less known than Doug Firs, WR Cedars and the strangely omitted Western Hemlock. I mean who puts Junipers on the list ahead of Western Hemlock? The king of White Wakanda is who.
Ponderosa can be found on the west side of the mountains but I don't think naturally. Mostly found in sporadic yards. The lodgepole pine is probably more common pine though especially on the eastern slope of the cascades and much of the okanogan and Idaho. Its much easier to find on the west side of the mountains as well.
Noble Firs are my go to Christmas tree. There's a great amount of them off the road to / from Mt. St. Helens. They are so symmetrical it adds an interesting look to the forest.
Yews are a great landscaping tree.
Junipers? Really?
My love for the Spruce mostly comes from this bad boy at the Hoh Rain Forest. Reminds me a lot of @PurpleBaze due to its girth and length.
-
WOODPurpleThrobber said:YellowSnow said:
I don't think they have a Ponderosa at the OR State Capital either. To damn moist for them in Salem.PurpleThrobber said:https://www.spokesman.com/stories/2023/may/08/ponderosa-pines-and-other-trees-of-eastern-washing/
The fags (Hi Bob Huggins) in Olympia just yesterday recognized that, in fact, there are trees in the 509 area code.
TTTTT, I know.
WAR PONDEROSA!!
WOOD!
Alas, my Ponderosas are bigger and better than yours (more sunshine) and the MILFS are richer and hotter.
The Gosser Ranch Milfs had a good chuckle at that. -
Douglas Fir
Blue spruce has been my favorite Christmas tree for as long as I can remember. They're sometimes easier to find around here than Noble, which tends to be above the snow line when I'm looking.huskyhooligan said:Partial to the Spruce. Little less known than Doug Firs, WR Cedars and the strangely omitted Western Hemlock. I mean who puts Junipers on the list ahead of Western Hemlock? The king of White Wakanda is who.
Ponderosa can be found on the west side of the mountains but I don't think naturally. Mostly found in sporadic yards. The lodgepole pine is probably more common pine though especially on the eastern slope of the cascades and much of the okanogan and Idaho. Its much easier to find on the west side of the mountains as well.
Noble Firs are my go to Christmas tree. There's a great amount of them off the road to / from Mt. St. Helens. They are so symmetrical it adds an interesting look to the forest.
Yews are a great landscaping tree.
Junipers? Really?
My love for the Spruce mostly comes from this bad boy at the Hoh Rain Forest. Reminds me a lot of @PurpleBaze due to its girth and length.
Plus nobody...cats, dogs, annoying people...fucks with a spruce Christmas tree. It's like getting jabbed with sewing pins. -
Ponderosa Pine
You got them big booty Sark relatives up there buying property? Yuck.PurpleThrobber said:YellowSnow said:
I don't think they have a Ponderosa at the OR State Capital either. To damn moist for them in Salem.PurpleThrobber said:https://www.spokesman.com/stories/2023/may/08/ponderosa-pines-and-other-trees-of-eastern-washing/
The fags (Hi Bob Huggins) in Olympia just yesterday recognized that, in fact, there are trees in the 509 area code.
TTTTT, I know.
WAR PONDEROSA!!
WOOD!
Alas, my Ponderosas are bigger and better than yours (more sunshine) and the MILFS are richer and hotter.
The Gosser Ranch Milfs had a good chuckle at that. -
Ponderosa Pine
Listen cum boi, the pole is the Western US, not just west of the crest and the Ponderosa is one of the most important trees of the west. Juniper is here to mix it up and have a little bio diversity in the pole and in terms of sq miles, probably more of them than any other tree out west.huskyhooligan said:Partial to the Spruce. Little less known than Doug Firs, WR Cedars and the strangely omitted Western Hemlock. I mean who puts Junipers on the list ahead of Western Hemlock? The king of White Wakanda is who.
Ponderosa can be found on the west side of the mountains but I don't think naturally. Mostly found in sporadic yards. The lodgepole pine is probably more common pine though especially on the eastern slope of the cascades and much of the okanogan and Idaho. Its much easier to find on the west side of the mountains as well.
Noble Firs are my go to Christmas tree. There's a great amount of them off the road to / from Mt. St. Helens. They are so symmetrical it adds an interesting look to the forest.
Yews are a great landscaping tree.
Junipers? Really?
My love for the Spruce mostly comes from this bad boy at the Hoh Rain Forest. Reminds me a lot of @PurpleBaze due to its girth and length.
My first White Wakanda Xmas tree was a 14' juniper that I cut down to size. My house smelled like Tanqueray Gin for a month.
Lodgepoles are boring and wimpy. -
Douglas Fir
"When we impacted, we bounced and bounced rather hard. We bounced along, landed on a couple of houses, took some telephone lines and some Douglas fir trees with us, and finally came to rest on two houses."
-my dad as quoted in the Washington Post after surviving the United crash at PDX in the late 1970s. -
RedwoodI did not know this
United Airlines Flight 173 was a scheduled flight from John F. Kennedy International Airport in New York City to Portland International Airport in Portland, Oregon, with a scheduled stop in Denver, Colorado. On December 28, 1978, the aircraft flying this route ran out of fuel while troubleshooting a landing gear problem and crashed in a suburban Portland neighborhood near NE 157th Avenue and East Burnside Street, killing 10 on board.[1][2][3][4][5]
Aircraft
The aircraft involved was a Douglas DC-8 60 series, powered by four Pratt & Whitney JT3D engines and delivered new to United Airlines in May 1968.[6] The aircraft was registered N8082U and was the 357th DC-8 built at the Long Beach assembly plant.[6] The 60 series was a stretched version of the DC-8 that was 36.7 ft (11.2 m) longer than the DC-8 series 10 through 50.[7]
Flight
Flight 173 was piloted by an experienced cockpit crew, consisting of Captain Malburn "Buddy" McBroom (age 52), First Officer Roderick "Rod" Beebe (45), and Flight Engineer Forrest "Frosty" Mendenhall (41). McBroom had been with United Airlines for 27 years; he was one of the airline's most senior pilots with more than 27,600 hours of flight time, of which about 5,500 hours had been as a DC-8 captain. Beebe had been with the airline for 13 years and had logged more than 5,200 flight hours. Mendenhall had close to 3,900 flight hours and had been with the airline for 11 years. The first officer and flight engineer had over 2,500 hours of flying experience between them in the DC-8.[8]
Flight 173 departed from Denver's Stapleton International Airport at 15:47 MST with 189 people on board—eight crew and 181 passengers. The estimated flight time was 2 hours and 26 minutes, and the planned arrival time in Portland was 17:13 PST, about 40 minutes after sunset. According to the automatic flight plan and monitoring system, the total amount of fuel required for the flight to Portland was 31,900 lb (14,500 kg). About 46,700 lb (21,200 kg) of fuel were on board the aircraft when it departed the gate in Denver.
As the landing gear was being lowered on approach to Portland International Airport, the crew felt an abnormal vibration and yaw of the aircraft and a lack of an indicator light showing the gear was lowered successfully. The crew requested a holding pattern to diagnose the problem, and for about the next hour, the crew flew over southeast Portland and worked to identify the status of the landing gear and prepare for a potential emergency landing. During this time, none of the three cockpit flight crew effectively monitored the fuel levels, which was exacerbated by the fact that the gear was down with the flaps at 15° during the entire hour-long holding maneuver, significantly increasing fuel burn rate. As a result, the number 3 and 4 engines flamed out.
As the crew prepared for a final approach for an emergency landing on runway 28L, they lost the number one and number two engines to a flameout, at which point a mayday was declared. This was the last radio transmission from Flight 173 to air traffic control; it crashed into a wooded section of a populated area of suburban Portland, about six nautical miles (11 km; 7 mi) southeast of the airport.[8]
Of the crew members, two were killed, flight engineer Mendenhall and lead flight attendant Joan Wheeler; two sustained injuries classified by the National Transportation Safety Board (NTSB) as "serious", and four sustained injuries classified as "minor/none". Eight passengers died, and 21 had serious injuries.[5][8]
The 304th Aerospace Rescue and Recovery Squadron of the Air Force Reserve, based at Portland International Airport, was conducting routine training flights in the area that evening. Airborne aircraft from this unit (HH-1H Huey helicopters) were immediately diverted to the crash scene and proceeded to transport many of the survivors to local hospitals.
Crash investigation and report
The NTSB investigation revealed that, when the landing gear was lowered, a loud thump was heard. That unusual sound was accompanied by abnormal vibration and yaw of the aircraft. The right main landing gear retract cylinder assembly had failed due to corrosion, and that allowed the right gear to free fall.[9] Although it was down and locked, the rapid and abnormal free fall of the gear damaged a microswitch so severely that it failed to complete the circuit to the cockpit green light that tells the pilots that gear is down and locked. Those unusual indications (loud noise, vibration, yaw, and no green light) led the captain to abort the landing, so they would have time to diagnose the problem and prepare the passengers for an emergency landing. While the decision to abort the landing was prudent, the accident occurred because the flight crew became so absorbed with diagnosing the problem that they failed to monitor their fuel state and calculate a time when they needed to return to land or risk fuel exhaustion.[9]
The Safety Board believes that this accident exemplifies a recurring problem—a breakdown in cockpit management and teamwork during a situation involving malfunctions of aircraft systems in flight… Therefore, the Safety Board can only conclude that the flight crew failed to relate the fuel remaining and the rate of fuel flow to the time and distance from the airport, because their attention was directed almost entirely toward diagnosing the landing gear problem.[8]
The NTSB determined the following probable cause:[8]
The failure of the captain to monitor properly the aircraft's fuel state and to properly respond to the low fuel state and the crewmember's advisories regarding fuel state. This resulted in fuel exhaustion to all engines. His inattention resulted from preoccupation with a landing gear malfunction and preparations for a possible landing emergency.
The NTSB also determined the following contributing factor:[8]
The failure of the other two flight crewmembers either to fully comprehend the criticality of the fuel state or to successfully communicate their concern to the captain
The fuel situation was known to be on the minds of the pilot and crew to some degree. Transcripts of cockpit recordings confirm this.[10] Media reports at the time suggested that a not widely known problem existed with fuel state gauges on that model aircraft.[citation needed] The problem was not widely known in part because commercial aircraft are expected to fly with no less than a 45-minute reserve of fuel at all times. The gauge problem is addressed, though obliquely, in one of the safety board's recommendations:
Issue an Operations Alert Bulletin to have FAA inspectors assure that crew training stresses differences in fuel-quantity measuring instruments and that crews flying with the new system are made aware of the possibility of misinterpretation of gauge readings. (Class II, Priority Action, A-79-32)
While the totalizer fuel gauge issue might have contributed to the crew's confusion toward the end of the flight, the NTSB report emphasized that the captain should never have allowed such a situation to develop in the first place. The NTSB made the following recommendation to specifically address that concern:
Issue an operations bulletin to all air carrier operations inspectors directing them to urge their assigned operators to ensure that their flightcrews are indoctrinated in principles of flight deck resource management, with particular emphasis on the merits of participative management for captains and assertiveness training for other cockpit crewmembers. (Class II, Priority Action, X-79-17)
Aftermath
This last NTSB recommendation following the incident, addressing flight deck resource management problems, was the genesis for major changes in the way airline crewmembers were trained. This new type of training addressed behavioral management challenges such as poor crew coordination, loss of situational awareness, and judgment errors frequently observed in aviation accidents. It is credited with launching the crew resource management[11] (CRM) revolution in airline training. Within weeks of the NTSB recommendation, NASA held a conference to bring government and industry experts together to examine the potential merits of this training.[12]
United Airlines instituted the industry's first CRM for pilots in 1981. This program is now used throughout the world, prompting some to call the United 173 accident one of the most important in aviation history.[13] The NTSB Air Safety Investigator who wrote the CRM recommendation was aviation psychologist Alan Diehl.[14][15]
Assigned to investigate this accident, Diehl realized it was similar to several other major airline accidents including United Airlines Flight 2860, which occurred a little over a year before Flight 173 and under near identical circumstances; Eastern Air Lines Flight 401; and the Tenerife airport disaster.[16] Diehl was familiar with the research being conducted at NASA’s Ames Research Center and believed these training concepts could reduce the likelihood of human error.[11][15][self-published source]
Held responsible for the accident, Captain McBroom lost his pilot's license and retired from United Airlines shortly afterwards. He spent his remaining years battling health problems related to injuries sustained in the crash, as well as lung and prostate cancers. Family members and passengers who spoke to McBroom at a 1998 reunion of crash survivors reported he was "a broken man" plagued by guilt over his role in the accident.[17] He died on October 9, 2004 at age 77.[18]
One of the surviving passengers, a three-year-old[19] in 1978, was awarded US$900,000 in damages from the airline by a Portland jury in 1984. She was injured and both her little sisters and her parents were killed.[20][21]
Published in February 2018, Crash Course by Julie Whipple[22] focuses on the events of the night of the crash, the investigation, and aftermath of the crash.
