Tuesday 30 December 2014

Beastly: Ford Trademarks EcoBeast Name, Possibly for 2016 Raptor

Leave a Comment
http://blog-admin.cddev.org/wp-content/uploads/2014/12/raptor-626x382.jpg
December 30, 2014 at 12:04 pm by | Photography by KGP Photography



2016 Ford F-150 SVT Raptor Spy Shot


Ford has trademarked the name “EcoBeast,” and to our ears, it sounds tailor-made for the next Raptor pickup.


The trademark filing on December 22, first reported by the blog Motrolix , appears to be a new take on Ford’s turbocharged EcoBoost engines that power nearly every Blue Oval product. But the nickname isn’t really new. F-150 and Focus ST owners have already coined the term, lovingly affixing to their vehicles “EcoBeast” stickers and badges that resemble the original factory graphics.


No matter. Ford forums are swirling about the 2016 Raptor packing a twin-turbo V-6, an EcoBoost poised to be so burly and bad that it’ll embarrass the previous truck’s 6.2-liter V-8. But while BMW can swap the old M3’s V-8 for a “TwinPower” six and still retain its dignity, a lower cylinder count sounds a bit degrading to a monster truck. EcoBeast could help squash any worry about the Raptor returning as a save-the-earth, goody two-shoes.






As nearly everyone is off for the holidays, we don’t have an official answer from Ford and we’re certain they wouldn’t talk about it anyway. Sure, EcoBeast could just be a marketing salvo to stop people from selling their own copycat badges that use Ford’s EcoBoost name in vain. Our intel is sniffing in the Raptor’s direction, and besides, it’s a name we’d like to stick on other Ford models. Next time someone asks, “What’s in your Fusion, bro?” we’ll say “Aw, nothin,’ just a 1.5-liter…EcoBeast!”



Other Stories You Might Like




This entry passed through the Full-Text RSS service - if this is your content and you're reading it on someone else's site, please read the FAQ at http://fivefilters.org/content-only/faq.php#publishers.






from Car and Driver Blog http://feedproxy.google.com/~r/caranddriver/blog/~3/AzXK5AuCqNM/

via IFTTT

0 comments:

Post a Comment