1970 Ford Ranchero Gt 5.8l on 2040-cars

Auto blog

Junkyard Gem: 1971 Mercury Comet 2-Door Sedan

When Ford introduced the original Maverick for the 1970 model year, Dearborn tradition required that a Mercury-badged version be created. That car ended up being the Comet, built from the 1971 through 1977 model years. Here's one of those first-year Comets in rough but recognizable condition, found in a Denver self-service yard not long ago. The Comet name had spent the 1960s affixed to the flanks of Mercurized Ford Falcons (1960-1965) and Fairlanes (1966-1969). Since the Maverick was the successor of the Falcon — sales of which went into an irrecoverable downward spiral once its sportier Mustang first cousin hit the streets — it made sense to move the Comet name over to the Mercury version. Nearly every American Mercury model ever sold was a U.S.-market Ford model with a different name and some gingerbread slapped on. Notable exceptions to this tradition include the 1999-2002 Mercury Cougar (mechanically based on the Contour but with a unique body) and the 1991-1994 Mercury Capri (an Australian-built mashup of Mazda components borrowed from the Ford Laser). The Comet was by far the cheapest Mercury model available in 1971, though it was considered more prestigious than its Maverick counterpart. The price tag on the '71 Comet two-door sedan started at $2,217 (about $16,505 in 2022 dollars), while the '71 Maverick two-door sedan cost $2,175 ($16,193 today). Meanwhile, AMC would sell you a new Hornet two-door sedan for one dollar less than a Maverick, Chevrolet had the Nova coupe for a dollar more than the Maverick, and Plymouth offered the Valiant Duster for $2,313 ($17,220 now). Toyota had a Maverick competitor as well that year, with the Corona at $2,150 for the sedan and $2,310 for the coupe. Having driven every one of the aforementioned models, I'd take the Duster if I went back in time and had to choose one (as a 1969 Corona owner, I'm not a fan of the 1971 facelift, though the Corona's build quality beats the Duster's). The build sticker on this car tells us that it was built at the Kansas City Assembly Plant (where Transits and F-150s are made today) and sold through the Los Angeles district sales office (there was a DSO in Denver, so it's a near-certainty that this car didn't start out in Colorado). The paint started out as Bright Blue Metallic (it's neither bright nor metallic 51 years down the road) and the interior was done up in Medium Blue Cloth & Vinyl.

Shelby GT500 laps N"urburgring in under 7:40?

A couple of weeks ago we brought you footage and official times of the new Chevy Camaro Z/28 lapping the Nürburgring. With a 7:37.47 lap time, the Z/28 emerged as the fastest muscle car ever to lap the circuit. But what was missing from that picture was how fast the king of all Mustangs, the Shelby GT500, could manage to lap the Nordschleife.
Ford never released any information or footage of the GT500 on the Nürburgring that we were aware of - that is, until the guys at SVTPerformance.com put in a request for Mustang videos. Among the clips they received was never-seen, in-car footage of the Shelby GT500 lapping the circuit. And boy did it hustle.
Although not quite official, the video seems to show the GT500 lapped the venerated German track in a touch under 7:40. That would make it a tick or two faster than the Camaro ZL1 - but what of the Z/28? By Chevy's quoted time, the Z/28 is still faster than the GT500, but SVTPerformance suggests GM may have fudged the numbers a bit and scrubbed half a second or so off their lap time.

Ford ditching Microsoft in favor of BlackBerry QNX for next-gen Sync?

Ask the average consumer - at least, those who follow the goings-on in the automotive industry - which carmaker they'd most closely associate Microsoft, and the answer you'd most likely get would be Ford. The Blue Oval automaker, after all, was at the forefront of bringing Microsoft technology into cars with its pioneering Sync system, and, though reality didn't turn out as such, Ford's CEO was recently touted as a potential future head of the Redmond-based software giant. But that relationship, according to the latest reports, could be coming to an end.
Alan Mullaly kiboshed the idea of leaving Dearborn for Redmond, but more importantly Ford is tipped to be ditching Microsoft in developing its next-generation Sync system. In its place, Ford is expected to partner with BlackBerry's QNX division.
Now, before you go balking "BlackBerry?! But they're finished!" consider that QNX is (or at least was) an independent entity that Research In Motion (as BlackBerry's Ontario-based parent company was then known) just happened to have bought back in 2010. QNX provides control systems to everything from nuclear power plants and UAVs to automakers like Audi, BMW and Porsche.