FANDOM


Tab-canon-white  Tab-legends-black  
"Well, it looks like Quadinaros is having engine trouble also."
Fodesinbeed Annodue[src]

The BT310 quadra-Podracer was a model of Podracer manufactured by Balta-Trabaat[1] that had four engines.[2] In the year 32 BBY,[4] the inexperienced Toong Podracing pilot Ben Quadinaros[5] rented[6] a hastily put together[5] BT310 for use in the Boonta Eve Classic,[6] an annual Podrace hosted on the planet Tatooine by the Hutts to commemorate the Boonta Eve holiday.[7] However, the quadra-Podracer suffered from an engine malfunction[8] that caused it to stall on the starting grid.[5] When its engines did ignite, the BT310's power couplings shorted out,[2] causing them to break loose and blast off in all directions[5] of Mos Espa Grand Arena,[2] destroying the Podracer.[8] Despite this, Quadinaros continued piloting a BT30 and was depicted using one in The Sport's Greatest Rivalry, a poster pitting him against his arch-rival, Sebulba.[9]

Quadinaros piloted a BT310 during the 29th Annual Bricklayers' Classic on Tatooine; as he was about to win the race, its engines broke lose as a Podracer piloted by Zander Freemaker collided with the quadra-Podracer, causing the Toong to lose.[10]

Behind the scenesEdit

"Ben Quadinaros, in the "Explode-At-The-Starting-Line-Mobile.""
―Fodesinbeed Annodue[src]

The BT310 quadra-Podracer was created for the 1999 film Star Wars: Episode I The Phantom Menace.[3] It was first identified in Ben Quadinaros's entry in the now-discontinued Encyclopedia on StarWars.com.[1]

It is likely that the BT310's "quadra-Pod" racing engines factored in the naming of Ben Quadinaros. It was realized as a detailed concept model and then rendered as a computer-generated vehicle.[11]

AppearancesEdit

Non-canon appearancesEdit

SourcesEdit

Notes and referencesEdit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.