Jump to content

Recommended Posts

Posted

Holy smokes... UPS plane crashed in Kentucky. It looks like people were hurt. :(

 

What the heck is going on - more planes have fallen out of the sky in the last year...

 

Maybe the FAA shouldn't have been Doge'd, maybe pay shouldn't be withheld from ATC's. I'm not saying that's the cause but it sure as heck isn't helping bolster safety.

  • Sad 1
Posted
3 minutes ago, Atlas said:

Holy smokes... UPS plane crashed in Kentucky. It looks like people were hurt. :(

 

What the heck is going on - more planes have fallen out of the sky in the last year...

 

Maybe the FAA shouldn't have been Doge'd, maybe pay shouldn't be withheld from ATC's. I'm not saying that's the cause but it sure as heck isn't helping bolster safety.

I retired from American Airlines and we were worried 20 years ago about quality pilots that were scratching and sniffing to claw way to majors. The military feed and critical screening is long gone. You make more $$ and get better lifestyle being in military than a pro pilot. We are getting bare minimum quality. I’m sure AI will correct all this need for professionalism. 🥹 

  • Sad 1
Posted
1 hour ago, Atlas said:

Holy smokes... UPS plane crashed in Kentucky. It looks like people were hurt. :(

 

What the heck is going on - more planes have fallen out of the sky in the last year...

 

Maybe the FAA shouldn't have been Doge'd, maybe pay shouldn't be withheld from ATC's. I'm not saying that's the cause but it sure as heck isn't helping bolster safety.

MD-11 a tricky jet to fly especially heavy ON TAKEOFF. We sold FEDEX and UPS ours when 777 finally showed up. 
Both have crashed them more frequently than any should have. Shelter in place a pretty serious order! Gee.  
 

https://www.lpm.org/news/2025-11-04/shelter-in-place-issued-in-louisville-following-reports-of-plane-crash

 

Posted
26 minutes ago, customboss said:

MD-11 a tricky jet to fly especially heavy ON TAKEOFF. We sold FEDEX and UPS ours when 777 finally showed up. 
Both have crashed them more frequently than any should have. Shelter in place a pretty serious order! Gee.  
 

https://www.lpm.org/news/2025-11-04/shelter-in-place-issued-in-louisville-following-reports-of-plane-crash

 

 

That sound serious. Also terrifying to think AI could be responsible for flying a plane someday - or would it reduce errors? I don't know. I've heard nothing good about people trying to make their way up the chain being commercial pilots. It's a tough gig, all-consuming, and the pay isn't there like it used to be.

  • Thanks 1
Posted
12 minutes ago, Atlas said:

 

That sound serious. Also terrifying to think AI could be responsible for flying a plane someday - or would it reduce errors? I don't know. I've heard nothing good about people trying to make their way up the chain being commercial pilots. It's a tough gig, all-consuming, and the pay isn't there like it used to be.

Seriously, hauling cargo and boxes going automated. As soon as the tech bros buy off the administration. PS AA never crashed a MD11. 

Posted
9 hours ago, txab said:

 

Looking at a takeoff catastrophic LH engine fire and seems the crew forgot to fly the jet. Fires are terrible and usually you don’t want to take it into air but he ran outta runway. Full of fuel. Vertical stab is a fuel tank too.  

Posted
On 11/4/2025 at 11:40 PM, txab said:

 

 

I saw last night the death toll is now 12 with 16 missing. Crew was only 3. That was allot of fuel. Will be interesting what the authorities find out. Truly sad event. 

  • Sad 1
Posted (edited)
1 hour ago, Grumpy Bear said:

 

I saw last night the death toll is now 12 with 16 missing. Crew was only 3. That was allot of fuel. Will be interesting what the authorities find out. Truly sad event. 

40,000 gallons if I recall. 

Edited by customboss
Posted

Interesting that the FAA decided the day after the crash to reduce commercial flights by 10%, stating they are doing it to maintain air safety. Pray for our air traffic controllers in these difficult times. They need relief.

  • Sad 1
Posted

IMG_0486.thumb.jpeg.c2d24ba890d6e53c63c41a7da2b8b3e9.jpeg

 

By Josh Evans 

 

Stephens Ford Flathead OHV conversion is one of the rarest and most fascinating performance adaptations ever developed for Ford’s famous Flathead V8. During the late 1940s and early 1950s, before Ford introduced its own overhead-valve engines, several independent engineers and speed equipment companies designed conversions to give the side-valve Flathead more breathing ability. Among these innovators was Bill Stephens, who developed a unique overhead-valve (OHV) cylinder head conversion that dramatically improved the Flathead’s performance and efficiency while maintaining its original block design.

Stephens’ conversion was designed to solve one of the Flathead’s biggest limitations restricted airflow caused by its valve-in-block layout. By moving the valves to the cylinder heads, the conversion allowed for more efficient combustion, higher compression ratios, and increased power output. The system replaced the original L-head cast-iron heads with custom aluminum heads that featured pushrod-actuated overhead valves, a rocker shaft assembly, and redesigned combustion chambers. This gave the Flathead characteristics similar to later overhead-valve V8s while retaining the iconic Ford block.

The Stephens OHV setup was produced in extremely limited numbers, primarily for racing applications and high-performance enthusiasts. It was seen as a competitor to other conversions of the era, such as the Ardun (designed by Zora Arkus-Duntov) and the Navarro OHV kits. However, the Stephens design was unique because it used a crossflow configuration, meaning the intake and exhaust ports were on opposite sides of the head, improving airflow and reducing heat buildup a common issue with traditional Flatheads.

Mechanically, a Stephens-converted Flathead could easily produce over 160 to 200 horsepower, depending on compression and carburetion a major improvement over the roughly 100 horsepower of the stock engine. Builders often paired the conversion with dual or triple carburetors, a high-lift camshaft, and custom headers to take full advantage of the improved breathing. The result was a smooth, powerful, and durable engine capable of competing with early overhead-valve V8s from Cadillac and Oldsmobile.

Today, a Ford Flathead with a Stephens OHV conversion is considered an extremely rare and valuable piece of hot rod history. Few complete examples survive, and when they appear at shows or auctions, they draw significant attention from collectors and historians. The Stephens conversion stands as a testament to the ingenuity of early American engine builders, who pushed the limits of what was possible with the original Ford Flathead design long before factory overhead-valve engines became the norm.

  • Like 1
Posted (edited)
3 hours ago, asilverblazer said:

To whom, your "false... fairytale" God?

 

Atheist I assume. An Agnostic believes he exist but doesn't care about his creation? Am I close?  

 

 

Edited by Grumpy Bear
Posted

Looks like UPS and FedEx grounded their fleets of MD-11, at least temporarily. Antiques that probably should have been retired years ago. But UPS especially penny pinches like nobody else. Have a few friends there and it does take a tragedy to get anything fixed. 🙄

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...