Pilot Report Pilatus PC 12NG

[video]

[video]

[video]

[video]

Zitat

I flew three separate sorties in rapid succession, from Buochs to Grenchen (LSZG), Grenchen to Zurich (LSZH) and Zurich to Emmen (LSME) to overshoot and land back at Buochs.
These flights were accomplished through complex and busy airspace, into airports varying from austere to international, with widely different runway sizes and using a wide variety of approach aids, visual circuits and approach angles. The sorties were flown manually and auto-pilot coupled, with go-arounds, normal landings, short landings, full stops and complete aircraft shutdowns at the end of each leg.
I flew all the sorties myself in the single pilot role. Michael Alb, my Pilatus safety pilot, only assisted me with the radio telephony, given my unfamiliarity with the local Swiss airspace.
On entering the cockpit, my first and strong impression was of how modern, well made, well laid out and uncluttered the Apex system made the whole cockpit feel.
All switches used during normal flight are forward of the power lever quadrant. The power lever combined the functions of throttle and prop RPM in a single lever so, additionally, the simplicity of the whole power quadrant added to the uncluttered cockpit impression.
I liked the grouping of the ice protection switches behind the left-hand pilot yoke and the design of the rocker switches, which made individual selection quick and simple.
Below the glare shield, well shaded and directly in front of the pilot was the communications control panel and centrally mounted was the autopilot control panel (ACP).
Both these panels featured small green indicator lights next to the selected button, which made nav/comm audio channel or ACP mode selections easy to confirm with just a glance.
This is in stark contrast to other systems that feature just "dumb" buttons on a black panel background and where incorrect ACP mode selections are easy to make, especially when the workload is high.
'DARK COCKPIT' PHILOSOPHY

The small overhead panel was principally to control the electrical system plus engine start, stall warning shaker/pusher test and external lights. Apart from turning the taxi/landing lights on or off pre-take off/post landing, there was no need for the pilot to use or check the overhead panel in normal flight. Apex keeps to a "dark cockpit" philosophy.
Pilatus has designed a standby electrical function, fed from one of the batteries, to supply just the lower navigation MFD screen with power for FMS programming pre-start without the risk of battery drain and without the need for external power, an auxiliary power unit or a running engine.
This means that the pilot can programme the FMS before the passengers arrive and so dramatically reduce his/her later workload. I found this function to be a real advantage.
Programming the Apex through the various phases of initialisation, take-off, cruise and approach was delightfully simple and logical.
The different flight phases are displayed as symbols and all data input is done "up front" without the usual multiple and hidden pages used in a conventional FMS where the input is required via a computer display unit.
As one data box in the lower MFD was filled and entered, the Apex system automatically jumped to the next. The FMS navigation route overlaid the waypoints on an electronic "real world" MFD map that showed terrain, lakes, airspace boundaries, and so on, and has the potential to show additional details like cities and roads if required.
The navigation MFD gave me a wonderful sense of situational awareness. I also liked the function of the joystick on the MFP to drive a cursor on the navigation MFD.
Post-start, with all screens illuminated, it is normal that the navigation MFD is switched to the top centre and the aircraft systems MFD selected to the bottom centre.
My first FMS programming (Buochs to Grenchen) took no more than 10min to complete pre-start, but later in the day the other sorties took no more than 3-5min to prepare and to insert all the route data as I quickly became familiar with Apex.
The before engine-start checks took just seconds to complete and consisted essentially of turning the batteries and fuel pumps on and pressing the engine-start button (there are no first-flight-of-day checks and most other test functions are automated).
Light up was instant, the condition lever was placed to ground idle, the flaps set to 15° and the stall warning system tested - and that was it.
Outside air temperature was 13°C and QNH 1,024hp. At brake release the power lever was simply placed fully forward to the stop, the torque limiter automatically protecting the pilot (since I slammed the power lever forward like a jet) and with no torque overswing observed throughout any of the sorties.

BRISK ACCELERATION

Take-off acceleration was brisk and the aircraft leapt into the air at the rotate speed of 85kt. After settling at the climb speed of 140kt, the initial climb rate was over 3,000ft/min (15.25m/s). LNAV was followed with autopilot coupled and a GPS overlay VOR/DME approach flown at Grenchen using vertical speed to follow an advisory VNAV profile.
I believe the ACP would benefit from a vertical speed "wheel" and a speed select knob allied to a displayed blue speed bug on the PFD vertical speed tape. Pilatus says it is considering this.
However, to keep things in perspective, I had just successfully completed, unaided as a single pilot, an advanced GPS/non-precision approach at an airfield I had never seen before, in an aircraft I had never flown before just 15min after my first take-off.
A go-around was then conducted at Grenchen to circle for Runway 07 visual circuits. The manoeuvre was simple and stress-free to accomplish by just pushing the go-around button in the power lever handle (the autopilot remains engaged and the go-around required pitch is automatically set), pushing the power lever forward to the stop, setting flap to 15, taking gear up and re-engaging LNAV.
Returning to the visual flight rules circuit and flying manually showed the aircraft to have fine mechanical control characteristics and the aileron servo-tabs seemed to have completely cured the earlier reported problems of heavy lateral control noted in the original PC-12s.
The landings at Grenchen showed the aircraft was in its element landing on a runway only 23m wide and stopping with "passenger comfort" within 500m from a VREF speed of 85kt.
On my second sortie I flew a high-speed instrument landing system approach (200kt initially, but reducing to 180kt due to ATC constraints) manually at Zurich Runway 14, slowing at around 5km (3nm) to configure and land with 15° flap at a VREF of 100kt.
On all these approaches I very much appreciated the layout of the Apex PFD, which groups flight, compass, TAWS, engine and navigation/communication information on one screen. It again reduced my workload by centralising information critical to the single pilot.

RETURN LANDINGS

For my return landings at Bouchs, after go-around at Emmen, Alb first demonstrated and I then flew a steep approach circuit, starting the finals turn from a 5,000ft downwind leg. The flaps at their full 40° setting and the prop in flight idle gave outstanding drag and speed stability to hold around an 8° approach angle and, with a pre-flare at around 100ft, the aircraft could be touched "on the numbers" at VREF with great accuracy. My final landing was a short landing from a normal circuit, touching at around 70kt and requiring no more than 350m of runway length.
On shutdown we had flown three complete sorties, with multiple approaches, circuits and go-arounds, a flight time of 1h 30min and we had used just 445kg of fuel.
The aircraft, with the new aileron servo-tab system, was light and responsive in all axes and a real joy to fly manually. The PC-12 NG's handling characteristics closely resembled those of the much smaller EADS Socata TBM 850. It was as easy to manoeuvre the PC-12 NG aggressively around a tight or steep approach visual circuit as it was to accurately track the guidance needles of the flight director on an ILS with the autopilot disengaged.
The increased power of the -67P allied to the torque limiter, single power lever, auto rudder trim and the almost instant power "bite" of the prop meant that the aircraft felt and handled like a jet, but with none of the jet engine "lag" when accelerating up from idle.
The power brake effect of the prop on landing was outstandingly effective allowing for very short landings without the need for virtually any wheel brakes during the landing roll and with none of the complications of lift dump, auto-brake or thrust reversers many jets require.
Additionally, the risk of foreign-object damage is greatly reduced with the intake inertial separator engaged, compared with the open intakes of similar size jets and especially when operating from austere, semi-prepared or unswept tarmac strips.
The PC-12 NG gave me the impression that it could safely and easily fly, with a single pilot, into or out of any sort of short strip of as little as 500m in length, surrounded by any sort of terrain, through some of the most congested and complex ATC environments, into any international airport, in a variety of configurations, on multiple sectors every day for the next 15 years and never miss a heartbeat.
With the ever-increasing price of oil and the recent resurgence of turboprops in the airliner market, it shows that turboprops can hold their own with jets in everything apart from ultimate top speed (if range considerations allows it) and ultimate cruise altitude (if ATC allows it), but cost their owners far less to run.
We were ready to taxi, with after-start and before-taxi checks complete, fully configured and fully programmed, less than 60s after pushing the engine-start button. On other turboprops, first-flight-of-day checks can take over 60min to complete.
Before take-off, the condition lever was set to flight idle, but the Apex configuration warning also ensures no miss trim or miss flap settings - an advanced feature for this class of aircraft. Weight at take-off was 4,100kg (9,000lb) - 3,000kg basic, 250kg crew plus cargo and 850kg fuel. Maximum take-off weight for the PC-12 NG is 4,745kg.

The PC-12 NG's combination of lower purchase price (Pilatus says it is about $1 million less to buy than the Beechcraft King Air B200 GT to a similar specification) and with up to 40% less direct operation costs than its nearest twin-engined turboprop competitor of similar size means that, in my view, the PC-12 NG has no real commercial competitor.
Any comparison with a jet of a similar size is meaningless because it becomes an "apples and oranges" argument between outright performance, capability and direct operating costs. Undoubtedly, the PC-12 NG will be as popular with the company chief financial officer to fund as it will be with the chief pilot to operate and the company executives to travel.
The avionics upgrade is by far the best upgrade to a presently certificated civil aircraft that I had ever had the good fortune of evaluating. With the Apex allied to the other aircraft upgrades of cockpit controls, engine power, electrical system, aileron servo-tab, pressurisation controller, and so on, it meant that the PC-12 NG truly felt like a new aeroplane rather than just an upgraded one.
The Apex is similar in functionality and display to the EASy cockpit. Apex is very intuitive, outstandingly easy to programme/manage and has a much better human vehicle interface than that presently offered by the older style electronic flight information system using a separate FMS, radio management unit and single-mode display screens.
Single pilot operation will always have some high workload areas, but the Apex system will be a massive workload reducer and safety provider.

CONCLUSIONS

I left Stans hugely impressed. I believe that, with this NG upgrade, Pilatus has raised the bar in this class of commuter aircraft.
Overall, I found that the PC-12 NG had a "look right, feel right, fly right" type of aura and was stacked with good design from nose to tail for pilot and passenger. I found it so good in all of the assessed areas of flyability, useability and affordability.

When the long-overdue EASA regulations governing single-engine IFR commercial operations are agreed and the survivability aspects can be properly addressed by all owners/operators from an internationally defined position, I believe the PC-12 NG has the potential to become a world beater.

Alles anzeigen

Vollständiger Text ist bei Flightglobal zu finden!

Toller Flieger!

Zitat von Navigator

Wenn da nur nicht das Single Engine Problem wäre.

Nun, wenn man single pilot unterwegs ist, erachte ich single engine als besser. Denn der zweite Motor bring dich im Allgemeinen zum Unfallort. Und was kurze Bahnen angeht, gibt es bessere Flieger wie die King Air und was Steigleistung und Reisegeschwindigkeit angeht sowieso.

[video]

Hier wird das geübt.

Ich gebe dir natürlich Recht, dass ne Twin an sich sicherer ist. Nur wenn man alleine vorne sitzt und man hat einen Ausfall auf einer Seite und hat schwierigere Randbedingungen ( Wetter etc) kann es m.E. schneller zu einem "Helmbrand" aka Überforderung kommen.

Und ein technischer Defekt an einer Turbine kann auch bei ner Twin oder einer Single auftreten.....Wie man hier eindrucksvoll lesen kann.Oder hier...

Soviel ich weiss gehört das zum Training .Bin mir aber nicht sicher und mache mich morgen schlau ....

Beech werkelt auch an einer single engine.....

Und gegen Pilatus haben die immer gelästert und die twin- Auslegung der King Air betont......
Das Einzige was mir ein wenig suspekt erscheint ist die Apex Suite als Avionik. Soviel Flieger haben das nicht drin und Honeywell hatte anfangs immense Probleme, während hingegen G1000 und Pro Line 21 zuverlässiger sind.....nicht zuletzt aufgrund des höheren Verbreitungsgrades, während die Apex Suite fast ein stand alone product ist.
Mal im Ernst, heutzutage gibt es keine schlechten Flieger mehr, wenn man es nüchtern betrachtet. Schon gar nicht in dieser Klasse.

Meine persönliche Wahl würde zwischen:

• Cheyenne 400 LS ( mit nem G1000 oder Pro Line 21 Retrofit) wegen Cruise und Range- Performance
• nem Jetprop Commander 1000 ( gerade die Renaissance Flieger mit dem Dash- 10 Upgrade der Triebwerke und dem Sound)
• einer Merlin 300( Reichweite und mit 737 Kutschern fast auf einer Höhe sitzend )
• der Pilatus PC 12 ( Frachttür)

fallen. Ich bin ein Fan der Garrett Triebwerke. Zudem wenn an sich die Anschaffungskosten für ne neue, vollausgestattete PC 12 anschaut, dagenen ne gebrauchte Merlin , Cheyenne oder Commander anschaut, sind die selbst mit einer extensiven Grundüberholung mit Avionik und Engine Upgrade, neuen Scimitar- Props von MT, günstiger in Anschaffung wie die PC 12. Im reinen Unterhalt ( Technik, Trainig usw) zwar teurer, aber wenn man bei der Anschaffung schon 800000 bis 1 Million spart, kann man lange für das Geld fliegen und bekommt mehr Flugzeug für weniger Geld.

Nun die 350er King Air ist ein gutes Flugzeug, keine Frage. Sie hätte auch ihre Daseinsberechtigung neben einer eventuell gebauten Starship.
Wenn man vergangene Entwürfe anschaut und sieht, wie selbst eine Cheyenne 400 einen CJ1 bestimmt und nen CJ2 vielleicht stehen lässt, und man dann sieht, wieviel davon gebaut wurde, ist es eine Schande. Alleine die Rückkaufaktion von den ganzen Starships von Beech war keine Sternstunde der Luftfahrt. Wenn ich mir den Hobel mit ner Garmin Suite oder Pro line 21 Suite vorstelle und eventuell mit Garretts hinten dran, dann bedauere ich die Ignoranz der Menschen.
Mit den Garretts muß man halt eben umgehen können ( die EGT ist da genau zu beobachten), wohin gegen die ehemalige Wasserpumpe PT6 selbst nen "ham- fisted pilot" glänzen lässt....
Piper ist nicht umsonst von der PT6 weg, um die 400er zu bauen.

Und eine 400er mit moderner Avionik und nem Dash- 10 Upgrade für die Triebwerke wäre ein Traum.
Scimitars von MT dran und los gehts.....einer von drei Turboprops , die nen Machmeter haben......

Die Garretts gingen halt schnell kaputt bei ISA+ wenn man im Hochsommer die Flieger abstellt und dann nicht noch mal von Hand durchdreht, damit die heisse Luft aus der Turbine gewedelt wird. Denn da hatten die ersten eine Neigung eine Unwucht in der Welle zu bekommem. Und meines Wissens nach halten ihre Leistungen in größeren Höhen wie die PT6.
Sogar Cessna hat damals in die Conquest II die Garretts reingebaut. Die ist der Corsair auf und davon geflogen.

Und es kommt natürlich drauf an, wie du deine Triebwerke behandelst. Das Einhalten der Torque- Limits ist da auch förderlich für ne lange Lebensdauer.

Und schon alleine der Sound....., hier an einer Reis- Rakete.....

Pilatus baute schon mal ne 2mot.....mal so am Rande....