Someone asked if I was enjoying it. Well it certainly is taxing and sort of satisfying in a way keeping the grey cells in work, but it’s not fun in the sort of way of being down the pub having had a few and then some 🙂
There is a level of difficulty to it but taken in parts there is nothing too complex that an average committed pilot (I guess) would not be able to cope with. However – but – although – mind you – the IR test is a short sector, some of which occurs outside of controlled airspace, so the Nav/RT massively ramps up the workload and does affect your ability to fly, maintain levels, headings etc. The same is true for the CPL.
If there’s one thing that the DA42 falls down on, its the inability (for a trainer) to have a nice A4 kneeboard placed on your lap without interfering with the stick. Your old A5 board is therefore used. Shame then you can’t go paperless and use the G1000.
You’ll see the above remarks borne out in session two from today. Incidentally a rough estimate to-date (inc today) for the IR has been about 14 sim sessions totalling around 24 hours. The course is structured for around 30 sim hours. So scarily I may be but a week away from the DA42 for the remaining 20 hours.
Tuesday 3rd July
Day 11
IR buddy is still away so two sessions for me today. The course is going faster than I expected.
Session 1
A little progress test. More of the same as the past few days. Depart Bristol for a Brecon 1Z SID, vectors back for hold, ILS approach for a go-around, engine failure, vectors back for a NDB DME approach still single-engine.
Of any points to make, again for the first approach I forgot to descend on the procedure passing the initial approach fix. Must have faith in making small changes when close to the ILS localiser or NDB; offset and wait for it to come back. Not doing so led to half scale deflections both right, left then right again. The finals check also includes a clearance Clarence, he tried to catch me out! We’ll also note that the ACA is above the DA, so theoretically you decide about single-engine committal to landing before cloud-break. In reality the examiner will have you flying down to DA.
Session 2
This is where it gets tough! Planned route is Bristol, SID to EXMOR, join the N864 airway, fly north to BCN, then break off the airway routing direct to OF at Filton. There do a hold, an ILS, go-around, engine failure, route West for general handling (two engines) i.e. base-turn/final stall. Then back to Bristol for an NDB DME (single-engine), missed approach and visual circle-to-land.
Apparently this was a test route at Bristol but is at present uncommonly used. I can see why 🙂
So this is simulating really a full test and cobbling the whole routine together. Had to do a full plog, create a CA48 Flight Plan vlaidating it on the CFMU website, research the airway levels using the AIP, print out all the possible terminal plates and this time include the aerodrome plate (having been starting from the hold before now). Headsets must be worn for the first time, to which I discover my DC squashing my swelled head and displacing my specs so affecting focus.
The start is made at Bristol Flight Centre (south side). Monitor ATIS, call Tower for start, shutdown avionics, start, request taxi, move northside crossing the active so it goes on as we are playing on a big boys’ field.
I could labour on about every point that went wrong, but I won’t. A cut to the chase therefore and notes I made from the debrief.
1. The active runway had a tailwind, the ILS if correctly identified would have shown this (not a deliberate challenge but a good lesson learnt).
2. Large altitude excursions, largely resulting I feel from doing other things other than flying e.g. paperwork and radio.
3. RT could be better, will have to delve into CAP413 when I have time and listen to e.g. liveatc.net.
4. Plan for the approach aids on the airway (I secretly dream about using the now-allowed autopilot on this sector)
5. Do pre-descent checks before descending, though I do remember do to them just after!
6. Filton ILS was messy and massively lost the glideslope about 1nm out. I explain that I didn’t know quite where the MAPt was on the plate (Aerad), so all went pear-shaped at a time when I should be devoting max concentration. Turns out the MAPt is inconspicuous so in the future I will highlight it in advance.
7. Planning ahead with the RT should be better. Busy busy aviating and navigating, but also having to sort the boys on the ground with Class G/D/airways trying to get details passed and airspace clearances. That mid-point sector over the Bristol Channel is just too busy with three airfields, two of them having own airspace and each with (at least) their own Approach and Tower frequency. Eeek.
Enjoying it? Well it certainly is taxing and sort of satisfying in a way keeping the grey cells in work, but it’s not fun in the sort of way of being down the pub having had a few and then some 🙂
There is a level of difficulty to it but taken in parts there is nothing too complex that an average committed pilot (I guess) would not be able to cope with. However – but – although – mind you – the IR test is a short sector, some of which occurs outside of controlled airspace, so the Nav/RT massively ramps up the workload and does affect your ability to fly, maintain levels, headings etc. The same is true for the CPL.
If there’s one thing that the DA42 falls down on, its the inability (for a trainer) to have a nice A4 kneeboard placed on your lap without interfering with the stick. Your old A5 board is therefore used. Shame then you can’t go paperless and use the G1000.
You’ll see the above remarks borne out in session two from today. Incidentally a rough estimate to-date (inc today) for the IR has been about 14 sim sessions totalling around 24 hours. The course is structured for around 30 sim hours. So scarily I may be but a week away from the DA42 for the remaining 20 hours.
Tuesday 3rd July
Day 11
IR buddy is still away so two sessions for me today. The course is going faster than I expected.
Session 1
A little progress test. More of the same as the past few days. Depart Bristol for a Brecon 1Z SID, vectors back for hold, ILS approach for a go-around, engine failure, vectors back for a NDB DME approach still single-engine.
Of any points to make, again for the first approach I forgot to descend on the procedure passing the initial approach fix. Must have faith in making small changes when close to the ILS localiser or NDB; offset and wait for it to come back. Not doing so led to half scale deflections both right, left then right again. The finals check also includes a clearance Clarence, he tried to catch me out! We’ll also note that the ACA is above the DA, so theoretically you decide about single-engine committal to landing before cloud-break. In reality the examiner will have you flying down to DA.
Session 2
This is where it gets tough! Planned route is Bristol, SID to EXMOR, join the N864 airway, fly north to BCN, then break off the airway routing direct to OF at Filton. There do a hold, an ILS, go-around, engine failure, route West for general handling (two engines) i.e. base-turn/final stall. Then back to Bristol for an NDB DME (single-engine), missed approach and visual circle-to-land.
Apparently this was a test route at Bristol but is at present uncommonly used. I can see why 🙂
So this is simulating really a full test and cobbling the whole routine together. Had to do a full plog, create a CA48 Flight Plan vlaidating it on the CFMU website, research the airway levels using the AIP, print out all the possible terminal plates and this time include the aerodrome plate (having been starting from the hold before now). Headsets must be worn for the first time, to which I discover my DC squashing my swelled head and displacing my specs so affecting focus.
The start is made at Bristol Flight Centre (south side). Monitor ATIS, call Tower for start, shutdown avionics, start, request taxi, move northside crossing the active so it goes on as we are playing on a big boys’ field.
I could labour on about every point that went wrong, but I won’t. A cut to the chase therefore and notes I made from the debrief.
1. The active runway had a tailwind, the ILS if correctly identified would have shown this (not a deliberate challenge but a good lesson learnt).
2. Large altitude excursions, largely resulting I feel from doing other things other than flying e.g. paperwork and radio.
3. RT could be better, will have to delve into CAP413 when I have time and listen to e.g. liveatc.net.
4. Plan for the approach aids on the airway (I secretly dream about using the now-allowed autopilot on this sector)
5. Do pre-descent checks before descending, though I do remember do to them just after!
6. Filton ILS was messy and massively lost the glideslope about 1nm out. I explain that I didn’t know quite where the MAPt was on the plate (Aerad), so all went pear-shaped at a time when I should be devoting max concentration. Turns out the MAPt is inconspicuous so in the future I will highlight it in advance.
7. Planning ahead with the RT should be better. Busy busy aviating and navigating, but also having to sort the boys on the ground with Class G/D/airways trying to get details passed and airspace clearances. That mid-point sector over the Bristol Channel is just too busy with three airfields, two of them having own airspace and each with (at least) their own Approach and Tower frequency. Eeek.
I can’t stress how behind the aircraft I felt, especially in relation to actual position so as to gauge proximity to CTAs. A tough exercise on the whole!
A good point made afterwards by the MCC instructor and former VC10 FO/RAF sim instructor. When you can, always think “WHAT NEXT?” repeatedly. Pays to stay ahead of the game.
Apparently it was a border-line IRT pass…
Day 9
Friday 29th June
More of the same with a SID, inbound terminal hold, LLZ/DME, go-around, engine failure and vectors back for an ILS.
Procedure was runway 09 at Scouseport, followed by the POL 5V SID then vectors in bound for the 09 ILS.
Points again were drift correction, configuration stabilised before the FAF/FAP the descent and doing a nice engine failure/shutdown routine. I did a PAN call of my own fruition this time though…
Day 10
Monday 2nd July
The weekend pre-brief was to prepare for a EXMOR 1Z departure from Bristol, followed by running down the airway toward Exeter and then being vectored off for the hold/08 NDB/DME approach again at Exeter.
This again with all the usual no viz on 1st approach, go-around, engine failure etc etc
The intention was to backseat first thing but sadly IR buddy had to be elsewhere so I get two sessions today and am threatened with three! Still, I’m not going to complain about a 2hr lunch break.
The session all goes pretty much to plan, some points made were thus. On the airway, have both NAVs tuned into the in-use VOR, one being the primary, the other a backup. The terminal procedure at Exeter nabbed me, the descent point passing EX is not at EX< rather 2d. Make sure the altimeter alerters are set for the missed approach altitude after going-around. Also pre-plan and check the asymmetric committal altitude, the final point where you decide to commit to landing single-engine, in advance for the field. Ops manual say 300ft agl so that needs adding to the field elevation.
Session 2
A BCN SID departure form Bristol runway 09, followed by a “simulated” i.e. no actual engine failure but as you would do for real in the aircraft without shutting the engine down. Then because the RVR at Bristol is set below the minimum for landing (800m min single-pilot ops) a diversion to a departure alternate, in this case Filton. Single-engine hold, then a NDB/DME to land on 09.
Extended too far on the outbound of the procedure and didn’t descend at the correct point. The reduced thrust on the “failed” engine is confusing when you have the good engine throttled back. It’s a job to remember which one you should use! Also whilst querying if to bring both throttles back whilst on final (if intending a go-around the dead engine cannot be advanced again) I go horrendously off-track and displaced north of the threshold. I could have made a landing in an emergency but decided to stay safe pushing the power forward.
Apart from that the session all goes pretty much to plan, some points made were to bug an anticipated heading before departure so as to maintain runway track. The wind was set strong and crossy. When levelling off on single-engine, get the power in sooner because of the inertia. I bust through the platform height pre-FAF because of this.
Anyone else find landing with a cross-wind in a simulator a bit weird? I had to resort back to basic PPL say out loud, “into wind elevator”, “opposite rudder”.
You’re giving the game away 😉
Ah Nimrod *sniff* Never leaves me with a dry eye and I always get goosebumps. Great video 🙂 🙂 🙂
I may get BoB2 now…
The CAA checked it yesterday and have issued a new certificate, do you think they might have missed something? 🙂
Day 8
Thursday 28th June
Another SID from Gatwick, a DME arc at Birmingham followed by a LLZ/DME approach to 05, go-around, engine failure and radar vectors for an ILS to land. All this with turbulence and a 25 knot wind for good measure.
Easy huh? 🙂
The SFD 8W SID was fairly straight-forward, there is only an ILS DME, a VOR and an ADF to tune. Unfortunately the Nav box on the sim cycles through the frequencies at .025khz at a time, so if you need a COM frequency in a hurry, forget it!
05 ILS/DME for Birmingham runway 05
DME arc at Birmingham first, not done one since first time practised them so initially I aimed the aircraft AT the beacon not 90degrees perpendicular to it. A few gentle turns keeps you roughly on the 10nm radius from Honiley VOR, nothing too taxing. The procedure though is fiddly, getting the ILS pre-tuned, identified and set on Nav 1 (which you are using for the arc) means you have to be quick in flipping over, checking and flipping back.
Glideslope fails so just a localiser LLZ/DME approach setting a rate of descent, cross-referencing the distances on the plate against altitudes. On the approach I try to get the gear and flap in earlier, seems a bit better but the power setting is elusive (modelling a PA34-220T). Will try even earlier say 1-1.5DME and holding level until 100knot is seen. A good approach leads to a good landing, but a good configuration leads to a good approach!
Engine failure after the go-around was a bit uggh. Spent too much time being quiet, getting the trim set properly before systems shutdown and thinking, rather than just doing blip-blip-blip methodically.
Single-engine ILS seemed a bit better and I pulled a greaser of a landing.
Approaches though still not within half-scale deflection all the way, as per test requires.
More of the same tomorrow, should also start using faux ATIS and entering onto a plog.
Day 7
Wednesday 27th June
The plan is to do a DVR 7B departure from Luton, followed by a quick reposition to perform the NDB/DME (short procedure) for Doncaster Sheffield Robin Hood Finningley.
The SID was easy enough, but the simulated turbulence was quite heavy and tough going. I had practised the SID beforehand though on MS Flight Sim. The procedure involves four VORs, so it can be easy to try intercept a radial on the wrong VOR, then wonder why it took you 15 minutes and half a county to do it in. I set the nav radios up so that Nav1 (on the HSI) tracked the most immediate beacon and the one after that was set on Nav 2. Come the relevant distance to the next radial, I could then track on Nav 2 whilst I got Nav 1 reconfigured.
The NDB procedure was a bit of a brain fart. Left-hand hold and because you hadn’t actually positioned yourself there, you have to work out where you are in relation to the plate. Initially I thought was coming in from the West when in fact I was coming in from the East. Having thought I sussed the 180 deg error out, I still had a brain fart figuring out about 30 seconds before I had decided on the wrong entry pattern. Thankfully there is a pause button. I’d also forgotten to ask for the wind, which was given in-flight and then forgot to apply the relevant drift corrections in the hold. But useful nonetheless, you won’t always accurately know what the wind is doing and fr better to see what’s happening by looking at how the RMI moves. Hold patterns therefore were a bit iffy.
The approach was I suppose acceptable not totally stable. Still need to find those power settings, I guess getting the aeroplane back to 100 knots before descending at the final approach fix/point would be better. Another small brain fart, I reached the MDA about a half mile before the missed approach point (MAPt) and decided to go around there. Technically you could fly to the MAPt then go-around. I dragged it just to make sure, but from that distance at MDA it is unlikely you will achieve cloud break, though in fog perhaps the extra half mile will benefit in poor visibility conditions. The sim as yet hasn’t or doesn’t do low viz.
Sure enough after the go-around, the engine fails (left). Untidy recovery, old habits really from being too focused, at least my foot was on the correct rudder pedal. I tend to leave the trimming to last so as to get the dead engine feathered asap so assisting performance. I initially forgot to check gear and flap up, then probably drifted off about 70 degrees by not concentrating enough on the DI whilst shutting down number 1’s systems (power, prop, mix, mags, alternators and fuel ****). Probably need to get the elevator and rudder trim set waaaay beforehand to be fair.
Coming inbound back to the NDB over the field and then the base turn again, I attempted another approach on 02 with a single engine. End up almost parallel to the threshold, technically a go-around situation but we explored the crash dynamics of the sim. I can report they are seriously feeble!
Apparently my IR buddy was exhausted just watching it. The lesson plan says I should be doing localiser-only approaches tomorrow.
thanks for the feedback 🙂
Taken 5 years ago on my first flying trip abroad.
I have some photos from the air 😉 I’ll dig them out if I can find them.
Day 6 Monday 25th
Progress test
The plan is to depart runway 16 at Halfpenny Green, track 270 on the WBA NDB until picking up the 360 track to the SWB Shawbury VOR. Upon approaching Shawbury, I will be vectored onto the southerly runway for an ILS. Then track outbound on the 110 deg radial from SWB back onto 180 QDM direct to Halfpenny Green for a NDB/DME procedure without hold to apporach runway 34. Then circle-to-land on 16.
All goes reasonbly to plan, however this is in Class G airspace so I am largely foxed by picking suitable flight levels based on track, it seems a large faff to keep adjusting your level by 500ft when intercepting a beacon. If you do too many things at once and don’t plan ahead enough, the instrument flying tolerances start to go out.
Tuesday 26th was a day-off, CAA inspection on the sim.
I thought the well-documented issue was the the man from the CAA turned up to do a flight test and upon starting had an engine fire?
‘NV was broken up last year. when in only 2003 she was stood outside in the sun at Coventry with nice new paint and two engines. 🙁
“Will it be at Legends?” 😉
Supermarine in Australia have evolved their Mk26 80% design into a Mk26b 90% design.
I wonder if they will go all the way to 100%?

Come to Daddy… 😀
Arguably the best handling in terms of stick waggling would be the lightest…
I’ve changed the thread title, just in case anyone thought Stapme was in the daisy bed. 🙂