Tuesday, December 30, 2014

Ford Trademarks 'EcoBeast' Moniker

Ford just filed a trademark for the


The days when FoMoCo used to stuff its high-performance vehicles with high-displacement V-8 engines are long gone, but that’s not to say the Blue Oval’s current offerings are of the slow variety. Although the 2015 Mustang still comes with a V-8 in its range-topping trim, several other nameplates — including the Focus and Fiesta ST, and the Taurus SHO — are motivated by EcoBoost technology. Be it with four or six cylinders, the EcoBoost engine has become the centerpiece of Ford performance and that’s not likely to change any time soon. In fact, it seems the EcoBoost is set to expand to other nameplates as well, judging by a trademark filing with the United States Patent and Trademark office.


According to the folks over at Motrolix, Ford has registered the term "EcoBeast" under the Goods and Services category of "Automobiles and automobile engines." This can only mean one thing; Ford is readying a new version of its turbocharged EcoBoost engine and judging by the name there’s something big coming our way; in terms of horsepower, that is!


So what are Ford intentions with this "EcoBeast" engine? The trademark filing provides no clue, but it’s very likely that this is a pickup truck application. You see, owners of F-150 pickups with the 3.5-liter, EcoBoost V-6 have been known to nickname their trucks "EcoBeast," and that’s solid indication that FoMoCo wants to emphasize on that moniker and use it for production purposes. And with the current 3.5-liter V-6 churning 365 horsepower, we have a feeling the "EcoBeast" will find its way into the next-generation SVT Raptor with more than 450 ponies at its disposal.


Click past the jump to read more about Ford’s new ’EcoBeast’ moniker.


Ford Trademarks 'EcoBeast' Moniker originally appeared on topspeed.com on Tuesday, 30 December 2014 14:00 EST.


read more










from Top Speed http://www.topspeed.com/cars/car-news/ford-trademarks-ecobeast-moniker-ar166867.html

via IFTTT

0 comments:

Post a Comment