FANDOM


Ash's Pidgeotto


Ash's Pidgeot was caught in the episode, Ash Catches a Pokémonas a Pidgeotto in the Viridian Forest. Then when he was heading to Orange Island to bring the GS Ball back to Professor Oak as requested on the way, there a bunch of Pidgey and Pidgeotto did not get along with some Spearows and a Fearow leading them then it appeared that the Fearow was the Spearow that Ash threw a stone at the start of his journey. Then Ash asked his Pidgeotto to convince the Pidgey and Pidgeotto that he wants to help them. When Ash'sPidgeotto was fighting against the Fearow and SpearowPidgeottowas hurt he suddenly evolved into a Pidgeot. When the Fearow was weak, Ash tried to catch it, but failed to do so. So with the help ofAsh's Pikachu, they were able to chase the Fearow away. Then Ash released his Pidgeot to protect the Pidgeotto and Pidgey promising to come back for it after he delivered the GS Ball, a promise he hasn't yet fulfilled.

Known movesEditEdit

Note: Season 1 means Generation 1 as well. This is before some moves went through Type changes.

Move Episode
[1]

 

Gust + Ash Catches a Pokémon
Quick Attack + Ash Catches a Pokémon
Sand-Attack Challenge of the Samurai
Whirlwind Clefairy and the Moon Stone
Wing Attack The Water Flowers of Cerulean City
Double-Edge The Battle of the Badge
+ indicates this Pokémon used this move recently.*

- indicates this Pokémon normally can't use this move.

TriviaEditEdit

  • Pidgeot is the first one of Ash's Pokémon that learned all of its moves in the evolution stage that he caught it in, and evolved later, the other one is Glalie.
  • Pidgeot is Ash's first Flying-type caught at the beginning of his journey.
  • Megumi Hayashibara who plays Team Rocket's Jessie in the Japanese-language version voices Pidgetto and Pidgeot in both the Japanese and English versions of the anime.

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.