Jump to content

231 down near Columbia River Gorge, Troutdale (KTTD)


Recommended Posts

Link to comment
Share on other sites

He turned base, lost the engine and was too far away to land . . . .

This is why so many people fuss at other pilots for flying bomber patterns. It's something that I have to watch, or I find myself well out of gliding range too, especially if the wind is 10 knots or more.

On the other hand, he apparently made a great emergency landing in the river, got out of the plane a d swam to the bank before Rescue arrived. Wonder if he raised the gear or not? We'll find out when the plane is raised.

Fly safe out there, ya'll!

  • Like 1
Link to comment
Share on other sites

12 minutes ago, Hank said:

He turned base, lost the engine and was too far away to land . . . .

This is why so many people fuss at other pilots for flying bomber patterns. It's something that I have to watch, or I find myself well out of gliding range too, especially if the wind is 10 knots or more.

On the other hand, he apparently made a great emergency landing in the river, got out of the plane a d swam to the bank before Rescue arrived. Wonder if he raised the gear or not? We'll find out when the plane is raised.

Fly safe out there, ya'll!

Yeah there's definitely not enough information in the article. We've all been pushed out on downwind by traffic doing straight-ins, getting cut off, someone doing an approach, or we were too fast and need to bleed off some speed, etc. Plenty of reasons to deviate from the norm just a bit. It's possible he just had an extended downwind for no reason, but who knows just yet. 

Link to comment
Share on other sites

13 minutes ago, RescueMunchkin said:

I was curious to see how long he'd been in the air for, but both flightaware and asdbexchange are showing no activity on the tail number yesterday.  Anybody know of a better way?

I was curious about that, too - since the aircraft is apparently ADS-B compliant, I thought maybe he's a 978mhz ADS-B out user who normally runs in anonymous mode.

Link to comment
Share on other sites

1 hour ago, RescueMunchkin said:

I was curious to see how long he'd been in the air for, but both flightaware and asdbexchange are showing no activity on the tail number yesterday.

I found other flights into TTD.  The last one I see was from June 14th.

 

Link to comment
Share on other sites

3 minutes ago, PeteMc said:

I found other flights into TTD.  The last one I see was from June 14th.

 

Really?  That one on June 14 was the only one I saw for this aircraft ever.  I thought maybe it was a discrete transponder code that required switching off anonymous mode.

ETA:  Sorry, there was also one in late July 2023 that had no details

Link to comment
Share on other sites

4 hours ago, natdm said:

Yeah there's definitely not enough information in the article. We've all been pushed out on downwind by traffic doing straight-ins, getting cut off, someone doing an approach, or we were too fast and need to bleed off some speed, etc. Plenty of reasons to deviate from the norm just a bit. It's possible he just had an extended downwind for no reason, but who knows just yet. 

Isn't Troutdale towered? Tapes should clarify what happened. 

Link to comment
Share on other sites

52 minutes ago, Hank said:

Isn't Troutdale towered? Tapes should clarify what happened. 

Troutdale is supposed to be towered, but they are low on resources there and are sometimes untowered during daylight hours.  

Looks like they were towered when the pilot departed - at approx 2138 UTC the KTTD controller advised 1VM to contact PDX Tower after departing and over the north bank (WA side of the Columbia River)

All times approximate in UTC

2211 - 231VM calls TTD tower to advise he's over the north bank inbound for landing.  Tower tells to advise when over the Washougal River.  Google maps shows the Washougal River is just about abeam the RWY 25 threshold

2214 - 231VM calls TTD tower to state he's crossing the Washougal River.  TTD tower tells 231VM to enter right base and clears to land RWY 25, winds 270@8.  231VM asks tower to repeat, tower does so more slowly and succinctly and adds that winds are 270@7.

About 1 minute later, 231VM calls and advises he's lost power.  Tower points out some blue hangars and asks if he's able to make it.  231VM responds "No I can't"

About 45 seconds later, TTD controller calls Helicopter 48A and asks if he can offer assistance flying over the downed aircraft.

 

Edited by RescueMunchkin
Adding more details
  • Like 1
Link to comment
Share on other sites

Interesting.  I fly into KTTD occasionally so I'm somewhat familiar with the area.  It sounds like he was arriving from the North to land, and when I do that I always just fly the approach directly into base, but the news reports the pilot as saying "“I was coming downwind to land in Troutdale. As I was turning to base..."

So I'm a little confused what was going on.    I would expect the ATC radio traffic is a more clear picture.

 

A approach from the North with a base that far out is very typical, at the North side of the Columbia river the Portland class C has a floor of 1,700' and even further North is only has a floor of 2,000'.   It's easiest to stay further East of that so you can descend at a normal rate rather than having to stay down below the C for so long.

Link to comment
Share on other sites

It appears that three (3) Mooney M20K's owned by this pilot have been destroyed in the last 4 years. Two of the crashes are documented in the Aviation Safety Network Database.  The N number's are the same and they are both M20K's but the planes are different model years with different serial numbers.  The third M20K was purchased between the 2 crashes.  There is no record of anything happening to it; however it wound up at BAS with bent wings. It is currently being sold for parts.

First M20K

1.jpg.15201c1da3442b18849e5708e7dd06b6.jpg

2.jpg.c299a8679842f7166de2feede34228ef.jpg

Second M20K  at 3,440 hours  https://www.aircraft.com/aircraft/205957049/n57241-1984-mooney-m20k-231se

image.jpeg.f86b6e331e179383464e70dd600b57a9.jpeg

Same plane at 3,445 hours

8.jpg.b928b522a7089632f3aea7639706d476.jpg

4.jpg.90436a4f5da04ac311030fb1f83f96ed.jpg

7.jpg.2095f7613db9f7763fc70a444f5302c9.jpg

 

Third M20K

Before N-number change.

9.jpg.0e46813af3d68a7827088d2c3a5b2dd5.jpg

 

After

10.jpg.5afc33f7f186641ad17086593ffe79c4.jpg

 

 

 

 

Edited by 1980Mooney
  • Like 4
  • Thanks 2
  • Haha 1
  • Sad 7
Link to comment
Share on other sites

9 hours ago, 1980Mooney said:

It appears that three (3) Mooney M20K's owned by this pilot have been destroyed in the last 4 years. Two of the crashes are documented in the Aviation Safety Network Database.  The N number's are the same and they are both M20K's but the planes are different model years with different serial numbers.  The third M20K was purchased between the 2 crashes.  There is no record of anything happening to it; however it wound up at BAS with bent wings. It is currently being sold for parts.

First M20K

1.jpg.15201c1da3442b18849e5708e7dd06b6.jpg

2.jpg.c299a8679842f7166de2feede34228ef.jpg

Second M20K  at 3,440 hours  https://www.aircraft.com/aircraft/205957049/n57241-1984-mooney-m20k-231se

image.jpeg.f86b6e331e179383464e70dd600b57a9.jpeg

Same plane at 3,445 hours

8.jpg.b928b522a7089632f3aea7639706d476.jpg

4.jpg.90436a4f5da04ac311030fb1f83f96ed.jpg

7.jpg.2095f7613db9f7763fc70a444f5302c9.jpg

 

Third M20K

Before N-number change.

9.jpg.0e46813af3d68a7827088d2c3a5b2dd5.jpg

 

After

10.jpg.5afc33f7f186641ad17086593ffe79c4.jpg

 

 

 

 

He has more lives than a cat. If he flies long enough he could wipe out the entire M20K fleet.

  • Like 2
  • Haha 5
  • Sad 3
Link to comment
Share on other sites

16 hours ago, toto said:

Really?  That one on June 14 was the only one I saw for this aircraft ever.  I thought maybe it was a discrete transponder code that required switching off anonymous mode.

ETA:  Sorry, there was also one in late July 2023 that had no details

 

17 hours ago, RescueMunchkin said:

I was curious to see how long he'd been in the air for, but both flightaware and asdbexchange are showing no activity on the tail number yesterday.  Anybody know of a better way?

 

17 hours ago, toto said:

I was curious about that, too - since the aircraft is apparently ADS-B compliant, I thought maybe he's a 978mhz ADS-B out user who normally runs in anonymous mode.

 

16 hours ago, PeteMc said:

I found other flights into TTD.  The last one I see was from June 14th.

If you look at the specs of N1172W which he bought in  September 2023 and renumbered it N231VM, it has a GTX 330-ES.  That has ADSB-out in 1090 MHz Extended Squitter (1090ES) which makes sense since it is a turbo that can operate above 18,000 ft. https://www.aircraft.com/aircraft/192905111/n1172w-1982-mooney-m20k-231

Something is screwed up with his ADSB registration.  His flight on Firday June 14 shows up 2 ways on FligthAware.  One is with ADSB signitures but registered as N131VM.  The other is without any ADSB and is registered as N231VM.

https://www.flightaware.com/live/flight/N231VM

https://www.flightaware.com/live/flight/N131VM

11.jpg.56460470d027d58cb22ce9a8af35fb5d.jpg

 

12.jpg.890a13c0f16aadc4c518e20916866ee0.jpg

 

13.jpg.9695cf832ec5fab121e0878b63479cb6.jpg

 

14.jpg.69361126ce9a6b73ef00eb614aad0825.jpg

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

45 minutes ago, LANCECASPER said:

He has more lives than a cat. If he flies long enough he could wipe out the entire M20K fleet.

Interesting comments that he made to FAA/NTSB in March 2020 NTSB CAROL Docket:

  • He reported that "he wasn't himself" and "not thinking"
  • "Things were happening too fast. I think I pulled back pressure on the yoke and with the plane in landing configuration, I think I stalleded the airplane and dropped the airplane onto the runway, The mains were fully deployed, however, I think that I put too much stress on the nose gear, and it broke off at the axle. The wheel went bouncing off the runway, which I saw. If it wasn't such a catastrophe, it would have been kind of funny."

Comments he made to press on Monday:

  • "I tried to restart the engine and it wouldn't restart, tried to switch tanks ... "
  • "I don't know if it's a miracle or just good piloting techniques," Boettcher said. "I don't know what but I did the right thing."
  • "I feel like I want to go home and go to bed and forget about it all," he said with a slight laugh.

These crashes don't seem to phase him.  I bet he buys another M20K.....

  • Like 1
Link to comment
Share on other sites

37 minutes ago, redbaron1982 said:

I expect he is going to get a very personalized insurance premium.... I don't want to pay for his mishaps!

N231VM (1982 MOONEY AIRCRAFT CORP. M20K owned by BOETTCHER RICHARD) Aircraft Registration - FlightAware

  • Boettcher had owned the original 1980 M20K, 25-0426 since 2006
  • 25-0426 crashed February 14, 2020
  • 1982 M20K, 25-0716 appears on M231VM registration on June 19, 2024 although he owned it since December 2020.

N57241 (1983 MOONEY AIRCRAFT CORP. M20K owned by BAS PART SALES LLC) Aircraft Registration - FlightAware 

  • Boettcher registered November 15, 2021 so purchased some time before. 
  • BAS picture above shows they received the wreckage February 11, 2022. 

N1172W (1982 MOONEY AIRCRAFT CORP. M20K owned by BOETTCHER RICHARD) Aircraft Registration - FlightAware

  • Boettcher registered December 6, 2022 so purchased some time before.
  • Registration indicates he moved to Ridgefield, WA on or before September 4, 2023
  • Changed N number to N231VM - some time after September 2023 and before this month.
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.