Vancouver chef Trevor Bird places second in Top Chef Canada season two

    1 of 1 2 of 1

      On Monday (June 4), Vancouver chef Trevor Bird placed second on Top Chef Canada season two. After 13 weeks of competition, 26-year-old Carl Heinrich, who was born in Sooke but now lives in Toronto, beat out 15 other chefs to claim the $100,000 prize, GE Monogram kitchen, and title of “Top Chef Canada”.

      During the hour and half season finale, the top-three finalists, which included Bird, Heinrich, and 27-year-old Jonathan Korecki from Ottawa, were surprised with a twist: three previously eliminated contestants were brought back to the competition to win a wild-card spot in the final elimination challenge. It was determined after cooking a three-course Prince Edward Island-inspired menu that 37-year-old Toronto chef David Chrystian would compete in final elimination challenge.

      To determine the winner, the chefs were required to create one final four-course meal that represented who they were as chefs at Ontario’s Hockley Valley Resort. Four previous competitors, including Whistler’s Jimmy Stewart, were brought back as sous chefs for the finale competitors.

      During the elimination challenge, Bird started by creating an amuse-bouche of fig, goat cheese, and pickled raspberry. This was followed by olive oil-poached arctic char and salad, roasted veal loin, and ended with a blueberry lavender tart.

      Judges during the finale episode included head judge Mark McEwen, restaurateur Shereen Arazm, host Lisa Ray, and Vancouver chef Vikram Vij.

      Chef Bird recently opened his first restaurant, Fable, with Top Chef Canada contestant Curtis Luk.

      You can follow Michelle da Silva on Twitter at twitter.com/michdas.

      Comments

      8 Comments

      earlnelly

      Jun 5, 2012 at 5:50am

      cuz 2 out of 3 aint bad.

      LisaB

      Jun 5, 2012 at 9:58am

      (minor correction: the challenge was a PEI theme, not NS; and Bird made a blueberry lavender tart)

      More importantly: Fable is really really good.

      Michelle da Silva

      Jun 5, 2012 at 10:02am

      Thanks LisaB. The article has been updated.

      Natty

      Jun 5, 2012 at 11:41am

      It was really rude to have posted this immediately after the show aired. A lot of people, including myself, watch the episodes online the next day. I didn't read the article last night but your headline gave it away. You could have at least had the decency to name it in a way that didn't spoil it for the rest of it. It's considered courtesy to give people a heads up when you're about to unleash spoilers.

      Paul.

      Jun 5, 2012 at 3:42pm

      @ Natty- Call me baffled, I'm not sure why there's so many minus votes at your comment. I'm an avid Top Chef Canada viewer. Everyone should note that this article was posted at 8:37pm on Monday evening. I was scrolling through the days articles on Straight around 9:00pm last night waiting for Top Chef Canada finale to start at 10:00PM Monday evening and saw this headline. It annoyed me too, not even a spoiler alert. Why post this BEFORE the finale even aired in Vancouver? It is unnecessary to post the results before the actual show is aired. So, thanks.

      Michelle da Silva

      Jun 5, 2012 at 3:48pm

      Natty and Paul, the Top Chef Canada season finale aired on Food Network Canada at 10 p.m. ET/PT, which means it aired at 7 p.m. PT, with an encore presentation at 10 p.m. PT.

      Natty

      Jun 5, 2012 at 8:15pm

      I'm sorry Michelle, but you have failed to justify the spoiler headline. You are free to post whatever story you want, when you want, but it *is* considered courtesy to alert people to show spoilers. In the case of TV episodes, no one would think you were "burying the lead" just because you didn't declare the outcome front and centre.

      Jared

      Jun 5, 2012 at 10:42pm

      I also happen to think it's common courtesy to offer up a spoiler alert. I read a fair bit about TV shows/ movies and I see spoiler alerts all the time. To me it's not a big deal but still ...