[velostar]

From what I understand DH was looking forward to retirement and was working hard to achieve that goal. I can’t imagine him not wanting to be away from aircraft though.

I don’t know the other guy but he certainly had passion for his banner towing from what I saw on his trip with the Flying Reporter.

A very sad incident but a stark reminder to be careful and always bear in mind that we never know when our time will be up so always be kind and don’t put off tomorrow what you can do today.

[G-BLEW]

In the late 80’s he was lured away from Broking to work with the CAA at Gatwick

If I remember correctly he was, for a time, the editor of GASIL

Ian

[john ball]

In the carefree days of the early 80’s, David and I flew a Super Cub and Rallye back from Aalst in Belgium which had been bought by Paul Nalson. It was an epic flight into a strong headwind and non radio. Memories of good times.

[Rob P]

Am I alone in finding it scary that in this age of moving map GPS an accident like this could happen?

Rob P

[matthew_w100]

DH and his then-wife Dorothy did my IMC/Night/twin ratings many years ago. Probably the best instructor I've ever flown with.

He'd just achieved his ambition of getting all his commercial flying and engineering licences, by IIRC his 40th birthday. Which seemed immensely old to me.

[Gas Guzzler]

Am I alone in finding it scary that in this age of moving map GPS an accident like this could happen?

Rob P

Probably not, but at this time we don't know if it was indeed CFIT , it may have been the result of engine or air-frame failure of some sort. Whether we will ever know for sure is debatable and we await the investigation findings I guess.

[Iceman]

Am I alone in finding it scary that in this age of moving map GPS an accident like this could happen?

Rob P

If you plot the named village in SD, for instance, there is no spot height given, but the nasty nature of the local terrain is shown in the vertical profile. This is pretty close to the destination San Sebastián. The Garmin 430 panel mount shown in the aircraft would not have had terrain by default.



Iceman

[Rob P]

The Garmin 430 panel mount shown in the aircraft would not have had terrain by default.

Thanks Mark, that starts to make a little more sense. No less sad though.

Rob P

[simon32]

I was in the area on Sunday and was glad I was in the car and not flying. The terrain is rugged and the peaks were shrouded. Not sure why they were so low as it would have been prudent to descend below the clouds over the sea which was not far away. His flight plan was filed via PPL (Pamplona), IFR I suppose, so they deviated nearing destination.

SA
09/01/2019 14:00->
METAR LESO 091400Z 04003KT 010V100 9999 BKN045 09/04 Q1026=
SA
09/01/2019 13:30->
METAR LESO 091330Z 07003KT 020V100 9999 BKN045 09/04 Q1026=
SA
09/01/2019 13:00->
METAR LESO 091300Z 08003G14KT 020V150 9999 BKN045 09/04 Q1027=
SA
09/01/2019 12:30->
METAR LESO 091230Z 09004KT 040V120 9999 BKN045 08/04 Q1027=
SA
09/01/2019 12:00->
METAR LESO 091200Z 06004KT 010V100 9999 BKN040 08/05 Q1028=
SA
09/01/2019 11:30->
METAR LESO 091130Z 08004KT 030V110 9999 BKN040 09/05 Q1028=
SA
09/01/2019 11:00->
METAR LESO 091100Z 10003KT 060V150 9999 BKN040 08/05 Q1028=
SA
09/01/2019 10:30->
METAR LESO 091030Z 07004KT 040V100 9999 BKN027 09/05 Q1029=
SA
09/01/2019 10:00->
METAR LESO 091000Z VRB02KT 9999 SCT017 BKN027 08/05 Q1028=
SA
09/01/2019 09:30->
METAR LESO 090930Z 07008KT 9999 BKN017 09/06 Q1028=
SA
09/01/2019 09:00->
METAR LESO 090900Z 06009KT 030V100 9999 BKN013 09/07 Q1028=
SA
09/01/2019 08:30->
METAR LESO 090830Z 06010KT 9999 SCT010 BKN015 09/07 Q1027=
SA
09/01/2019 08:00->
METAR LESO 090800Z 29005KT 240V340 9999 SCT015 BKN030 11/07
Q1027=

Simon

[PeteSpencer]

If you plot the named village in SD, for instance, there is no spot height given, but the nasty nature of the local terrain is shown in the vertical profile. This is pretty closeu to the destination San Sebastián. The Garmin 430 panel mount shown in the aircraft would not have had terrain by default

Iceman

Ice:

(My italics)

Could you clarify your assertion re 430 terrain please

Peter

[Iceman]

The standard Garmin 430 / 530 does not have a terrain database by default that it displays on the screen. There is an add-on database for the 530 (I had it in the Commander), can't remember if available for the 430, that presents red / yellow colour-coded screen if the aircraft should come within certain vertical limits of the surrounding terrain. Alerts would be generated to this effect and you could view this terrain warning screen. I am not sure of the resolution of the terrain database and therefore whether or not is was necessarily capable of 'seeing' very narrow peaks. The 430/530 does of course display the MSA for the route.

More details available in the manual.



Iceman

[GrahamB]

A 430 (no terrain) and a 430W (terrain plus other features) will look exactly the same in the panel, you can’t tell which model one is until you switch it on.

[PeteSpencer]

The reason I ask is that the 430W has Terrain as standard , with two options to display 360 deg terrain or a 120 deg arc ahead (60 deg either side of flight path.)

The terrain page always defaults to 'track 'up'.

There is often discussion on PPLIR about the difficulty in updating the Terrain page on the 430W , requiring, as it does, a completely separate card and reader, to the extent that most 430W owners don't bother to update on the basis that mountains rarely move.

Our 430W certainly has terrain as standard when installed 5 years ago which manifests itself a bright red and yellow markings and shouty text when landing....

Peter

[Iceman]

A 430 (no terrain) and a 430W (terrain plus other features) will look exactly the same in the panel, you can’t tell which model one is until you switch it on.

Yes, old 430 assumed for my comment on optional terrain awareness database to hold true.

Iceman

[highfive]

Truly devastating news, so many happy days flying G-ARVU and his Mooney.

RIP.