If You Grew Up In The ’70s, You Definitely Remember These Cars






As a car enthusiast, growing up in the 1970s was bittersweet. While there were some cool looking muscle cars from the early ’70s in dealer showrooms, the muscle car era’s heyday was mostly behind us as we slipped into the malaise era fueled by stricter emissions controls and rising gasoline prices.

However, that’s not to say the 1970s lacked its share of memorable cars. And we don’t just design holdovers from 1960s. Some the entries on this played roles on the silver screen or the smaller screens in our living rooms. Some are remembered because of the foundation they laid for models that are still with us over 50 years later, and other are remembered simply for their quirkiness.

We’ll present five memorable cars from the 1970s in this list, but first there’s an honorable mention that’s not included because it isn’t strictly a car. General Motors’ square body pickups are some of the best looking trucks ever designed. The design marked the third generation of Chevrolet and GMC C- and K-series trucks which rolled out for the 1973 model year. With that out of the way, let’s return to the list of memorable 1970s cars.

The 1974 Plymouth Roadrunner

If you grew up in 1970s America, or potentially other parts of the world as well, and you were already a fan of powerful cars, you likely watched “The Dukes of Hazzard” on television each week. While the General Lee, a bright orange late 1960s Dodge Charger, several of which were destroyed while filming, and cousins Bo and Luke Duke were the stars of the show, many remember another Duke, Daisy.

One of the most interesting things about Daisy Duke, aside from her wardrobe which inspired an entire generation, was what she drove. While the show didn’t debut until the late 1970s, the first car we saw Daisy driving was a 1974 Plymouth Roadrunner. Like the one pictured above, Miss Duke’s Roadrunner was bright yellow with a black racing stripe extending from near the headlights, down the fenders, across the doors, and onto the quarter panels before wrapping around the rear side windows and extending over the top.

We can only guess at the storyline-power of Daisy’s 1974 Roadrunner after her cousins tuned it to their liking. However, even real world specs for the car show it potentially had the 440 cubic-inch big block V8 engine equipped with a four-barrel carburetor putting out a likely underrated 275 SAE net horsepower.

1978 Silver Anniversary Corvette Pace Car

Another car that got the primal blood of 1970s youngsters simmering was the Official Pace Car Edition of the Silver Anniversary 1978 Chevrolet Corvette. While there are other special edition Chevy Corvettes that will always turn heads, this one marked 25 years of Corvette, and was the first of the brand act as a pace car in America’s biggest race.

The first time many saw this special Corvette livery was at the start of the 1978 Indianapolis 500 as it aired on television. Seeing its gleaming black over silver two-tone paint, red pinstriping, polished aluminum wheels, front and rear spoilers, with the words “Official Pace Car” on the door is a core memory for more 1970’s kids than you might guess (myself included).

The model came along 10 years into the C3 generation. It didn’t bring any significant changes to the underlying ‘Vette, but the updated styling and celebratory year contributed to record production numbers at the time. 

The Chevrolet Corvette Silver Anniversary Pace Car edition replica accounted for 6,502 (one for each Chevrolet Dealership at the time) of the nearly 47,000 Corvette coupes built for the 1978 model year. Base MSRP for the standard 1978 Corvette coupe was around $9,352, while opting for the Indy 500 Pace Car replica upped the starting price to $13,353. Buyers had a choice between two 350 (5.7-liter) small block Chevy engine options: the L48 with 185 hp, or the L82 with 220 hp. Transmission options included a four-speed manual or three-speed automatic.

The 1973 Honda Civic

It’s not memorable as one of the best looking hatchbacks ever designed, but the 1973 Honda Civic is cemented in the memories of 1970s kids. The car made an impression as being among the first cars we’d remember as economical by design that are still with us today.

As kids in the early 1970s, we didn’t care much about gas prices. What we remember is seeing the long lines of cars, and people standing with gas cans in hand, at gas pumps. The introduction of the Honda Civic to the United States was a direct response to that fuel crisis. Compared to the late 1960s and early 1970s muscle cars sitting in nearly every parking lot of the time, the 1973 Civic wasn’t much to look at, but that’s probably why we remember seeing them as they became more common.

The March 1973 issue of Car and Driver carried news of the new Honda Civic with the prediction it would “start something big.” The author of that headline had no way of knowing just how big the Civic’s impact on the future of cars would be.

The 1973 Civic’s transverse-mounted 1.2-liter four-cylinder provided 50 hp and 50 lb-ft of torque through the four-speed manual transmission. While relatively low-powered, the lightweight four-passenger Civic could accelerate to 60 mph in just under 13 seconds and had a top speed of 88 mph.

The Ford Pinto

The ill-fated Ford Pinto made its debut for the 1971 model year. While it’s widely regarded as one of the worst-looking Fords ever made, its looks aren’t the primary reason people who grew up in the 1970s remember it. Yes, it was kind of ugly, but there were uglier cars around, like the AMC Pacer for example.

The real reason the early 1970’s Ford Pinto is engrained into memory is its likelihood of catching fire when hit from the rear. The first instance occurred in 1972 in California when a Ford Pinto was struck from the rear with an impact speed of 28 mph, ultimately killing the driver and burning a 13-year-old passenger, Richard Grimshaw, over 90% of his body. Over 100 lawsuits arising from similar incidents followed.

Surprisingly, production of the Ford Pinto carried on throughout the 1970s before Ford pulled the plug in 1980. Ford Motor Company issued a recall for 1.5 million Ford Pintos and another 30,000 Mercury Bobcats because their fuel tank design put them at risk of fiery rear-end crashes.

The jury in the Grimshaw case originally awarded the young man $125 million in punitive damages because Ford Motor Company knew the fuel tank design was dangerous before the Pinto went into production. The design remained because the company calculated it was cheaper to pay claims for any associated injuries or deaths than to implement a better design, a design for which Ford already held a patent.

The Smokey and the Bandit replica 1977 Pontiac Trans Am

There are few classic muscle cars from the movies that are more recognizable than the 1977 Pontiac Trans Am driven by Burt Reynolds in “Smokey and the Bandit.” In the classic hit movie, the Trans Am is able to deliver a performance that cuts through the endless background chatter about runaway brides and the illegal transportation of alcohol. Honorable mention goes to Fred (a basset hound) for his fine performance as well.

For 1977, the Pontiac Trans Am received a facelift. The Trans Ams used in the movie were actually 1976 models, but they were equipped with updated 1977 front clips, featuring two pairs of rectangular headlights, to make them appear as new models.

The top trim W72 1977 Trans Am featured a 6.6-liter Pontiac engine with 200 hp and 325 lb-ft of torque. Transmission options included a four-speed manual or three-speed automatic.

To find an original Smokey and the Bandit replica Trans Am, look for non-T-top 1977 and 1978 models with an RPO code of Y81 or Y82 for T-tops. The front fascia of the 1979 Trans Am saw some big changes once again, but RPO Y84 models with a four-speed gets close to the original Bandit car.





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


  • Law establishes national prohibition against nonconsensual online publication of intimate images of individuals, both authentic and computer-generated.
  • First federal law regulating AI-generated content.
  • Creates requirement that covered platforms promptly remove depictions upon receiving notice of their existence and a valid takedown request.
  • For many online service providers, complying with the Take It Down Act’s notice-and-takedown requirement may warrant revising their existing DMCA takedown notice provisions and processes.
  • Another carve-out to CDA immunity? More like a dichotomy of sorts…. 

On May 19, 2025, President Trump signed the bipartisan-supported Take it Down Act into law. The law prohibits any person from using an “interactive computer service” to publish, or threaten to publish, nonconsensual intimate imagery (NCII), including AI-generated NCII (colloquially known as revenge pornography or deepfake revenge pornography). Additionally, the law requires that, within one year of enactment, social media companies and other covered platforms implement a notice-and-takedown mechanism that allows victims to report NCII.  Platforms must then remove properly reported imagery (and any known identical copies) within 48 hours of receiving a compliant request.

Support for the Act and Concerns

The Take it Down Act attempts to fill a void in the policymaking space, as many states had not enacted legislation regulating sexual deepfakes when it was signed into law. The Act has been described as the first major federal law that addresses harm caused by AI. It passed the Senate in February of this year by unanimous consent and passed the House of Representatives in April by a vote of 409-2. It also drew the support of many leading technology companies.

Despite receiving almost unanimous support in Congress, some digital privacy advocates have expressed some concerns that the new notice-and-takedown mechanism could have some unintended consequences for digital privacy in general.  For example, some commentators have suggested that the statute’s takedown provision is written too broadly and lacks sufficient safeguards against frivolous requests, potentially leading to the removal of lawful content –especially given the short 48-hour time to act following a takedown request.  [Note: In 2023, we similarly wrote about abuses of the takedown provision of the Digital Millennium Copyright Act]. In addition, some have argued that the law could undermine end-to-end encryption by possibly forcing such companies to “break” encryption to comply with the removal process.  Supporters of the law have countered that private encrypted messages would likely not be considered “published” under the text of the statute (which uses the term “publish” as opposed to “distribute”).

Criminalization of NCII Publication for Individuals

The Act makes it unlawful for any person “to use an interactive computer service to knowingly publish an intimate visual depiction of an identifiable individual” under certain circumstances.[1] It also prohibits threats involving the publishing of NCII and establishes various criminal penalties. Notably, the Act does not distinguish between authentic and AI-generated NCII in its penalties section if the content has been published. Furthermore, the Act expressly states that a victim’s prior consent to the creation of the original image or its disclosure to another individual does not constitute consent for its publication.

New Notice-and-Takedown Requirement for “Covered Platforms”

Along with punishing individuals who publish NCII, the Take it Down Act requires covered platforms to create a notice-and-takedown process for NCII within one year of the law’s passage. Below are the main points for platforms to consider:

  • Covered Platforms. The Act defines a “covered platform” as a “website, online service, online application, or mobile application” that serves the public and either provides a forum for user-generated content (including messages, videos, images, games, and audio files) or regularly deals with NCII as part of its business.
  • Notice-and-Takedown Process. Covered platforms must create a process through which victims of NCII (or someone authorized to act on their behalf) can send notice to them about the existence of such material (including a statement indicating a “good faith belief” that the intimate visual depiction of the individual is nonconsensual, along with information to assist in locating the unlawful image) and can request its removal.
  • Notice to Users. Adding an additional compliance item to the checklist, the Act requires covered platforms to provide a “clear and conspicuous” notice of the Act’s notice and removal process, such as through a conspicuous link to another web page or disclosure.
  • Removal of NCII. Within 48 hours of receiving a valid removal request, covered platforms must remove the NCII and “make reasonable efforts to identify and remove any known identical copies.”
  • Enforcement. Compliance under this provision will be enforced by the Federal Trade Commission (FTC).
  • Safe Harbor. Under the law, covered platforms will not be held liable for “good faith” removal of content that is claimed to be NCII “based on facts or circumstances from which the unlawful publishing of an intimate visual depiction is apparent,” even if it is later determined that the removed content was lawfully published.

Compliance Note: For many online service providers, complying with the Take It Down Act’s notice-and-takedown requirement may warrant revising their existing DMCA takedown notice provisions and processes, especially if those processes have not been reviewed or updated for some time.  Many “covered platforms” may rely on automated processes (or a combination of automated efforts combined with targeted human oversight) to fulfill Take It Down Act requests and meet the related obligation to make “reasonable efforts” to identify and remove known identical copies.  This may involve using tools for processing notices, removing content and detecting duplicates. As a result, some providers should consider whether their existing takedown provisions should also be amended to address these new requirements and how they will implement these new compliance items on the backend using the infrastructure already in place for the DMCA.

What about CDA Section 230?

Section 230 of the Communications Decency Act (“CDA”), 47 U.S.C § 230, prohibits a “provider or user of an interactive computer service” from being held responsible “as the publisher or speaker of any information provided by another information content provider.” Courts have construed the immunity provisions in Section 230 broadly in a variety of cases arising from the publication of user-generated content. 

Following enactment of the Take It Down Act, some important questions for platforms are: (1) whether Section 230 still protects platforms from actions related to the hosting or removal of NCII; and (2) whether FTC enforcement of the Take It Down Act’s platform notice-and-takedown process is blocked or limited by CDA immunity. 

On first blush, it might seem that the CDA would restrict enforcement against online providers in this area, as decisions regarding the hosting and removal of third party content would necessarily treat a covered platform as a “publisher or speaker” of third party content. However, a deeper examination of the text of the CDA suggests the answer is more nuanced.

It should be noted that the Good Samaritan provision of the CDA (47 U.S.C § 230(c)(2)) could be used by online providers as a shield from liability for actions taken to proactively filter or remove third party NCII content or remove NCII at the direction of a user’s notice under the Take It Down Act, as CDA immunity extends to good faith actions to restrict access to or availability of material that the provider or user considers to be “obscene, lewd, lascivious, filthy, excessively violent, harassing, or otherwise objectionable.” Moreover, the Take It Down Act adds its own safe harbor for online providers for “good faith disabling of access to, or removal of, material claimed to be a nonconsensual intimate visual depiction based on facts or circumstances from which the unlawful publishing of an intimate visual depiction is apparent, regardless of whether the intimate visual depiction is ultimately determined to be unlawful or not.” 

Still, further questions about the reach of the CDA prove more intriguing. The Take It Down Act appears to create a dichotomy of sorts regarding CDA immunity in the context of NCII removal claims.  Under the text of the CDA, it appears that immunity would not limit FTC enforcement of the Take It Down Act’s notice-and-takedown provision affecting “covered platforms.” To explore this issue, it’s important to examine the CDA’s exceptions, specifically 47 U.S.C § 230(e)(1).   

Effect on other laws

(1) No effect on criminal law

Nothing in this section shall be construed to impair the enforcement of section 223 or 231 of this title [i.e., the Communications Act], chapter 71 (relating to obscenity) or 110 (relating to sexual exploitation of children) of title 18, or any other Federal criminal statute.

Under the text of the CDA’s exception, Congress carved out Section 223 and 231 of the Communications Act from the CDA’s scope of immunity.  Since the Take It Down Act states that it will be codified at Section 223 of the Communications Act of 1934 (i.e., 47 U.S.C. 223(h)), it appears that platforms would not enjoy CDA protection from FTC civil enforcement actions based on the agency’s authority to enforce the Act’s requirements that covered platforms “reasonably comply” with the new Take It Down Act notice-and-takedown obligations.

However, that is not the end of the analysis for platforms.  Interestingly, it would appear that platforms would generally still retain CDA protection (subject to any exceptions) from claims related to the hosting or publishing third party NCII that have not been the subject of a Take It Down Act notice, since the Act’s requirements for removal of NCII by platforms would not be implicated without a valid removal request.[2]  Similarly, a platform could make a strong argument that it retains CDA immunity from any claims brought by an individual (rather than the FTC) for failing to reasonably comply with a Take It Down Act notice.  That said, it is conceivable that litigants – or event state attorneys general – might attempt to frame such legal actions under consumer protection statutes, as the Take It Down Act states that a failure to reasonably comply with an NCII takedown request is an unfair or deceptive trade practice under the FTC Act.  Even in such a case, platforms would likely contend that such claims by these non-FTC parties are merely claims based on a platform’s role as publisher of third party content and are therefore barred by the CDA. 

Ultimately, most, if not all, platforms will likely make best efforts to reasonably comply with the Take It Down Act, thus avoiding the above contingencies.  Yet, for platforms using automated systems to process takedown requests, unintended errors may occur and it’s important to understand how and when the CDA would still protect platforms against any related claims.

Looking Ahead

It will be up to a year before the notice-and-takedown requirements become effective, so we will have to wait and see how well the process works in eradicating revenge pornography material and intimate AI deepfakes from platforms, how the Act potentially affects messaging platforms, how aggressively the Department of Justice will prosecute offenders, and how closely the FTC will be monitoring online platforms’ compliance with the new takedown requirements.

It also remains to be seen whether Congress has an appetite to pass more AI legislation. Less than two weeks before the Take it Down Act was signed into law, the Senate Committee on Commerce, Science, and Transportation held a hearing on “Winning the AI Race” that featured the CEOs of many well-known AI companies. During the hearing, there was bipartisan agreement on the importance of sustaining America’s leadership in AI, expanding the AI supply chain and not burdening AI developers with a regulatory framework as strict as the EU AI Act. The senators listened to testimony from tech executives calling for enhanced educational initiatives and the improvement of infrastructure needed for advancing AI innovation, alongside discussing proposed bills regulating the industry, but it was not clear whether any of these potential policy solutions would receive enough support to be signed into law.

The authors would like to thank Aniket C. Mukherji, a Proskauer legal assistant, for his contributions to this post.


[1] The Act provides that the publication of the NCII of an adult is unlawful if (for authentic content) “the intimate visual depiction was obtained or created under circumstances in which the person knew or reasonably should have known the identifiable individual had a reasonable expectation of privacy,” if (for AI-generated content) “the digital forgery was published without the consent of the identifiable individual,” and if (for both authentic and AI-generated content) what is depicted “was not voluntarily exposed by the identifiable individual in a public or commercial setting,” “is not a matter of public concern,” and is intended to cause harm or does cause harm to the identifiable individual. The publication of NCII (whether authentic or AI-generated) of a minor is unlawful if it is published with intent to “abuse, humiliate, harass, or degrade the minor” or “arouse or gratify the sexual desire of any person.” The Act also lists some basic exceptions, such as publications of covered imagery for law enforcement investigations, legal proceedings, or educational purposes, among other things.

[2] Under the Act, “Upon receiving a valid removal request from an identifiable individual (or an authorized person acting on behalf of such individual) using the process described in paragraph (1)(A)(ii), a covered platform shall, as soon as possible, but not later than 48 hours after receiving such request—

(A) remove the intimate visual depiction; and

(B) make reasonable efforts to identify and remove any known identical copies of such depiction.



Source link