Norwegian HEMS Landing Wirestrike
Norwegian HEMS Landing Wirestrike (Norsk Luftambulanse EC135P2+ LN-OOI) On 14 January 2013, a HEMS / air ambulance Airbus Helicopters EC135P2+, LN-OOI of Norsk Luftambulanse, crashed near an entrance to Sønsterud tunnel in Hole municipality, Buskerud County, Norway. The pilot and a doctor on board were killed. The HEMS Crew Member (HCM) survived with serious injuries. History of the Accident Flight According to the Accident Investigation Board Norway (AIBN) investigation report (issued in June 2015), the helicopter and its crew were on standby at Lørenskog, Oslo when a call was received to attend an overturned lorry 21 nm away near Sollihøgda on the E16. The aircraft was airborne 9 minutes after the ambulance control took the 112 call. The Aircraft Commander was in the front right seat, the HCM in the front left seat and a physician, as a medical passenger, in the right-hand cabin seat. En-route, the physician received the accident site coordinates via the fleet management system LOCUS used by the emergency medical communication centre. The HCM set a course for position 595950N 0101810E in the helicopter’s digital map system ([EuroAvioincs] EURONAV [5]) and the course to the traffic accident site was displayed on the cockpit multi-function display. The crew were “very familiar” with the destination but the HCM “followed the procedures regardless and zoomed in on the possible landing site on the moving map display”. He noticed an adjacent powerline. The pilot acknowledged it and the doctor was also informed for situational awareness. They tried calling the emergency services on site at the road accident (on Channel 33 – VHF ‘Medical’)) without success. The aircraft was also fitted with radios for the digital emergency network (TETRA). This was not however in use in that district at the time. The introduction of TETRA elsewhere had been problematic due to weak management of change and crews had become use to often landing without having achieved radio contact with ground units. After a ten-minute flight, the helicopter arrived at the scene of the traffic accident which had occurred between the exits of the Nes and Sønsterud tunnels. The aircraft commander reduced the speed to 50 kt and flew approx. 200 m south of the site, in a south-western direction, at approx. 800 ft. altitude above the ground (1 461 ft. MSL) in order to find a suitable landing area. According to the HCM, they flew relatively fast and high, and were not on particular lookout for any aviation obstacles [and] he and the aircraft commander agreed to land on the road by the southern exit of the Nes tunnel [where there was an emergency lay-by]. A survey of the operator’s employees conducted by AIBN after the accident confirmed this was a reasonable site, considering the obstacles the crew had spotted (a line of streetlights and a coincident low powerline). After passing the landing site, the helicopter continued on a south-western course, at the same time as it descended to 700 ft. (MSL) and made a wide right turn. It then slowly continued towards the landing site in a north-eastern direction. [The operator’s OM-A (Operations Manual Part A General)] does not describe a special procedure for landing in areas where the moving map indicates that there is a power line or other aviation obstacles. OM-A also does not contain a description of how the crew should use their eyes to look for aviation obstacles in the most critical final part of approach and landing. On...
read moreA109E Window Loss Highlights Maintenance Lessons
A109E Window Loss Highlights Maintenance Lessons During a post-maintenance flight over Cornwall on 27 June 2019, of Leonardo A109E, G-ETPI, as the helicopter was accelerated towards 140 kt, there was a loud bang and a sudden increase in wind noise. The window transparency from the left cockpit door had separated. The pilot was able to land the aircraft safely. According to the Air Accidents Investigation Branch (AAIB) in their safety investigation report: The A109E cockpit doors are of a composite construction and include a non-opening single acrylic window transparency…attached to the door by an extruded rubber seal channel. The rubber seal has three separate grooves to accommodate the window, the door frame and a seal filler strip which locks the seal and window in place. The Maintenance Manual requires that a thin layer of adhesive is applied to the seal channel during installation. During the previous maintenance the aircraft had been repainted… …which necessitated the removal and disassembly of all cockpit and cabin doors and windows. These tasks were documented as a single item on a maintenance worksheet, which was signed-off by the certifying engineer on 21 March 2019. Following completion of the helicopter base maintenance and repaint, the doors and windows were reassembled and refitted by an engineer. The worksheet did not record the date on which the task had been completed but indicated that it had been inspected and certified by the certifying engineer on 9 April 2019. During examination of the window aperture afterwards it was not possible to confirm that adhesive had been used. The window and seal were never recovered so could not be examined. The right cockpit door window was removed for inspection and this revealed the correct presence of adhesive in the grooves of the seal. Inspection of the cabin windows confirmed adhesive had been used but “minimal squeeze-out”and so extra adhesive was applied. However: The post-incident inspection and reinstallation of the cockpit door windows was undertaken by the same engineer and certifying engineer who had done the original window installation in April 2019. The maintenance organisation carried out their own investigation, which only started after the post-incident inspection: It identified that the engineer who installed the left cockpit door window had experienced some difficulty fitting the seal filler strip to the seal channel. The engineer had used a soapy solution to insert the filler strip but acknowledged during the investigation that the solution was applied liberally, such that it covered the window and the concentration of soap had been stronger than might normally be used. The C537 adhesive specified in the A109E maintenance manual is a multi-purpose silicone adhesive/sealant which adheres to most surfaces and cures to form a tough flexible rubber. A single 310 ml tube of adhesive was issued to G-ETPI during its original maintenance input. …a similar tube of adhesive with approximately 1 inch of adhesive remaining was found in the hangar. It was determined that this was the originally-issued tube of adhesive and that it had been used during the original and post-incident window installations on G-ETPI. The maintenance organisation considered that, applied in correct quantity, the original and post-incident installation of all the cabin, cockpit and cockpit door windows would have required more adhesive than that which appeared to have been used. It would also have expected to see residual adhesive on the...
read moreRunway Excursion Exposes Safety Management Issues
Runway Excursion Exposes Safety Management Issues On 7 January 2019 RAF-AVIA Saab 340B YL-RAF, positioning from the airline’s base at Riga in Latvia veered off the runway during the landing roll at Savonlinna Airport in Finland. The Accident Flight The Finnish Safety Investigation Authority (SIAF, the Onnettomuustutkintakeskus) explain in their safety investigation report that: The runway had been cleared of snow but the clearance had to be repeated to achieve better runway friction. The aircraft had to wait for the landing in the holding pattern, and the landing was delayed. At the time of the landing it was dark, a crosswind was blowing, it was snowing and the runway was slippery. The approach proceeded normally until the aircraft passed the threshold. At the final phase of the landing the aircraft floated close to the surface for 6–7 seconds before touchdown, following which the touchdown point moved farther down the runway than normally. Extra airspeed after the threshold partly contributed to this. The captain steered the aircraft toward the ground at a fairly high vertical speed. At that time the aircraft was already over the snowbank at the edge of the cleared area of the runway. Despite the pilot’s corrective control actions the aircraft veered off the runway into the snowbank. The flight crew comprised of two pilots and a ground engineer. Nobody was injured but the aircraft suffered significant damage. They comment that: At no time did the pilots consider aborting the approach or landing, i.e. going around. The airline’s operational manuals (OM-A and OM-B) were inconsistent concerning maximum crosswind components. According to the Operations Manual (OM-A) the crosswind limits given by the Aircraft Operations Manual (OM-B) must be followed during landing. However, the OM-A also says that if the estimated runway friction is poor, crosswind landings are prohibited. In other words, then the crosswind component should be zero knots. In this occurrence the AFIS officer informed the pilots that the runway friction was poor. The instructions were difficult to follow in practice. The investigation was hampered because: The Cockpit Voice Recorder had not recorded anything from the flight in question, and the earlier recordings that were retrieved from its memory were of extremely poor quality. The recording quality of the FDR, when compared to modern recorders, was poor. The magnetic tape of the FDR was worn, which caused defects in the recording. The SIAF describe a phenomena where: When snow is blowing sideways, a pilot may see an illusion when approaching the runway where the aircraft’s track is deviating from the intended track or the runway bearing. The illusion is stronger at nighttime when the aircraft’s landing lights are on. The Contractual Arrangement, Due Diligence, Safety Management and Regulation The airline had a contract from Finnish ground handling and logistics company Maavoima who had won the tender for the subsidised Helsinki–Savonlinna public service obligation route in April 2017. The contract was awarded by the Finnish Transport Agency to the lowest bidder. The FTA had stipulated no safety requirements beyond the requirements that the air operator hold a regulatory approval for fear that safety requirements would be seen as ‘anti-competitive’. SIAF highlight that the lack of additional safety requirements was the FTA’s choice. Furthermore, as prime contractor… …Maavoima relied on the fact that air operator certificates and operating licences ensure that the air operator acts in a...
read moreEC130B4 Destroyed After Ice Ingestion – Engine Intake Left Uncovered
Airbus EC130B4 Destroyed After Ice Ingestion – Engine Intake Left Uncovered (Air Methods, N334AM) On 2 January 2013, Eurocopter EC130B4 HEMS air ambulance helicopter N334AM, operated by Air Methods, experienced a hard landing following a loss of power from its Turbomeca Arriel 2B1 turboshaft engine near Seminole, Oklahoma. The pilot and three medical crew members were all seriously injured. The US National Transportation Safety Board (NTSB) say in their final report, that according to the pilot, the crew… …received a standby call for a response to an accident scene. The pilot checked weather for the flight. He went and removed the helicopter inlet cover and the flight was requested to launch. The pilot performed a walk around inspection of the helicopter and started the helicopter normally. Shortly after takeoff, while climbing through 1,600 and 1,700 feet mean sea level (msl), the pilot heard a sound like something had struck the helicopter and the engine stopped producing power. The pilot had limited recollection of the next events but recalled that while performing an autorotation, he made a right turn to an open field. While maneuvering to land to the field he saw a previously undetected barbed wire fence. The pilot maneuvered the helicopter over the fence and [a] crew member reported seeing the sky through the forward windscreen before they impacted the ground. According to the NTSB Airworthiness Group report: The location of the ground scars relative to the final resting position of the aircraft was consistent with a clockwise rotation of the aircraft of approximately 180 degrees following initial ground impact of the landing skids and the tail skid. A barbed-wire fence was located approximately 16 feet west of the single tail skid ground scar and approximately 54 feet west of the main wreckage. The NTSB explain that: Engine examination revealed that the four axial compressor blades exhibited significant deformation on the outboard tips of their leading edges in the direction opposite of normal rotation consistent with the ingestion of soft body foreign object debris, such as ice. Investigation however revealed that: For 3 days before the accident flight, the helicopter was parked outside without its engine cover installed and was exposed to light drizzle, rain, mist, and fog. The engine inlet cover was installed the day before the accident at an unknown time. The helicopter remained outside and exposed to freezing temperatures throughout the night until 2 hours before the flight. Although the helicopter was maintained in a ready status on the helipad and maintenance personnel performed daily preflight/airworthiness checks, the inlet to the first-stage of the axial compressor was not inspected to ensure that it was free of ice in accordance with the Aircraft Maintenance Manual. The NTSBconclude that: Based on the weather conditions that the helicopter was exposed to during the 3 days before the accident, it is likely that ice formed in the engine air inlet before the flight and that, when the pilot increased the engine power during takeoff, the accumulated ice separated from the inlet and was ingested by the engine and damaged the compressor blades. NTSB Probable Cause The loss of engine power due to ice ingestion. Contributing to the accident was maintenance personnel’s delayed decision to install the helicopter’s engine inlet cover until after the engine had been exposed to moisture and freezing temperatures and their inadequate daily preflight/airworthiness checks, which did not detect the ice formation....
read moreCosta Rican C208B Stalled While Trying To Avoid High Ground
Costa Rican C208B Stalled While Trying To Avoid High Ground (Nature Air TI-BEI) On 31 December 2017, Cessna 208B Grand Caravan TI-BEI, operated by Nature Air, crashed while manoeuvring after takeoff at Islita Airport (MRIA), near Corozalito, Costa Rica. The 2 flight crew and 10 passengers (all 10 US tourists) were fatally injured. There was a post crash fire. The Accident Flight The C208 was the second of a pair of C208Bs transporting hotel guests from MRIA to Juan Santamaría International Airport (MROC), San Jose, where most of the passengers had connecting international airline flights. The US National Transportation Safety Board (NTSB), who were delegated this accident investigation, say in their safety investigation report that: The flight departed a nontower-controlled airport that was in a valley surrounded on all sides by rising terrain, with the exception of the area beyond the departure end of runway 21, which led directly toward the Pacific Ocean. The airport had a single paved runway, runway 3/21, that was about 3,000 ft long and 30 ft wide. The…first airplane departed runway 3…and made an immediate right turn to the east/southeast after takeoff, following a pass in the hills over lower terrain that provided time for the airplane to climb over the mountains. Both a witness and surveillance video footage from the airport indicated that, 15 minutes later, the accident airplane also departed from runway 3 but instead continued on runway heading, then entered a left turn and descended into terrain. Evaluation of the surveillance video was performed using a computer program……groundspeed was estimated to be 68±3 kts shortly after takeoff and the airplane was climbing about 715 ft/minute. Several seconds later, the airplane was descending about 1,510 ft/minute and its groundspeed was 82±4 kts. Its bank angle reached up to 75º right-wing-up at that time; the airplane impacted the ground shortly thereafter. The Pilot’s Operating Handbook (POH) for the airplane listed a gross weight stall speed at 60° bank with 0° and 20° flap settings as 110 kts calibrated airspeed (kcas) and 98 kcas, respectively. NTSB Analysis Although a takeoff from runway 21 afforded the most favorable terrain since the airplane would fly over lower terrain to the ocean, it is possible that a significant enough tailwind existed for runway 21 that the pilots believed the airplane’s maximum tailwind takeoff limitation [10-kt] may be exceeded and chose to depart from runway 3 in the absence of any information regarding the wind velocity. The investigators note that no windsocks were installed at the airfield at the time of the accident. Wind models at 10 meters above ground level indicated that, for the time of the accident, the wind was about 5 knots from the northeast. Performance calculations showed that the airplane would have been able to take off [on runway 21] with up to a 10-kt tailwind, which was the manufacturer limitation for tailwind takeoffs. The witness who saw the accident reported that he spoke with the pilots of both airplanes before the flights departed and that the pilots acknowledged the need to use the eastern pass in order to clear terrain when departing from runway 3. The reason that the flight crew of the accident airplane failed to use this path after takeoff could not be determined. It is likely that, after entering the valley ahead of the...
read moreFatal Powerline Human External Cargo Flight
Fatal Powerline Human External Cargo (HEC) Flight (Winco H369D N138WH) On 7 November 2017 Hughes 369D helicopter, N138WH operated by Winco Powerline Services under Part 133 regulations, was lifting two electricity utility linesmen on an external cargo long line. as Human External Cargo (HEC). The long line contacting a shield wire suspended between power transmission towers near Sulphur, Louisiana. The long line severed and the two linesmen were fatally injured when they fell around 100 ft to the ground. According to the US National Transportation Safety Board (NTSB) investigation report (issued November 2019): …the purpose of the flight was to install guard ropes between the deenergized 500-kilovolt power transmission lines before the existing braided steel shield wire from the nearby transmission tower was replaced. The east/west power transmission lines, with three sets of bundled conductors (northern, center, and southern), crossed perpendicular over a road. The pilot reported that, following a preflight safety briefing, he and one of the linemen discussed the expected work tasks. The pilot stated that, following their discussion, he brought the helicopter into a hover to allow the linemen to hook onto the external cargo long line. He then repositioned the helicopter to allow the linemen to work on the center conductor bundle. …after the linemen had tied off the guard rope to the center conductor bundle, he repositioned the helicopter to allow work on the northern conductor bundle. The pilot reported that he saw the long line contact the braided steel shield wire as one of the linemen held onto the northern conductor. The long line severed as the pilot turned the helicopter into the wind and attempted to move the linemen away from the northern conductor. The pilot reported that, immediately before the long line severed, he observed one of the linemen tugging at the conductor to reposition the guard rope perpendicular to the conductors. After the long line severed, the pilot returned to the landing zone and made an uneventful landing. The 60-ft long line separated about midspan. The pilot was 71 and had… …had accumulated 25,090 total hours of flight experience, of which 21,063 hours were logged as pilot-in-command and 11,286 hours were flown in Hughes 369 helicopters. The helicopter was operating under Part 133 Class B during the flight according to the operator (i.e. with a jettisonable load). The linesmen were considered as crew, not passengers, during powerline construction operations. The operator reported that: The FAA had approved the helicopter’s hook installation; however, because the flight was conducted under Part 133 Class B, the FAA did not regulate, specify, or approve the long line or the harnesses that was used to hoist the two linemen. In 2018 the FAA issued Safety Alert for Operators (SAFO) 18013 Updated Rotorcraft External Load Attaching Means and Quick Release Devices for Human External Cargo (HEC). This prohibited Part 133 operators from conducting HEC operations with attaching means not certificated to HEC requirements contained in Parts 27 and 29. This specifically related to a Portable Safety Device (PSD), also known as a Belly Band System or emergency anchor, that serves as a backup system to the primary hook, even if the hook kit is not certified for HEC. This affected MD500/Hughes 369 operators in particular. The operator reported that the long line was a 7/16 inch Amsteel Blue synthetic rope made of Dyneema SK-75 synthetic fiber that had...
read moreSeason’s Greetings from Aerossurance
Aerossurance sends its Season’s Greetings to all its customers, partners, suppliers, colleagues and friends. We also wish you all a safe and prosperous 2020! For aviation advice you can trust, contact Aerossurance at: enquiries@aerossurance.com Follow us on LinkedIn and on Twitter @Aerossurance for our latest...
read moreBK117B2 Air Ambulance Flameout: Fuel Transfer Pumps OFF, Caution Lights Invisible in NVG Modified Cockpit
Air Methods Airbus BK117B2 HEMS Air Ambulance N238BK Flameout: Fuel Transfer Pumps OFF, Caution Lights Invisible in NVG Modified Cockpit Just after sunset on 1 July 2017 an Air Methods Corporation Airbus Helicopters BK117B2, N238BK, conducting a Part 135 inter-hospital patient transfer air ambulance flight, landed hard and rolled over during a forced landing in a field outside Perryville, Missouri. The pilot, the three medical personnel and the 5 year old patient all received minor injuries. History of the Accident Flight The aircraft was established in cruise at 120 kts and an altitude of 1600 ft AMSL (approximately 1200 ft AGL). According to the US National Transportation Safety Board (NTSB) investigation report, the pilot stated that… …about 17 minutes after takeoff while in cruise flight at dusk, the helicopter “experienced a sharp change in attitude yawing to the left with a hard-upward bump,” followed by a change in engine noise. He saw that the engine gas generator speed (N1) gauges for each engine were indicating below 40% and decreasing and that the No. 1 engine low warning light, the No. 1 generator light, and the battery discharge warning lights were illuminated. …the helicopter suddenly “pitched nose up and rolled to the right” and that he then heard the rotor speed begin to deteriorate. He entered an autorotation by applying right forward cyclic and lowering the collective to full down. During the autorotative descent, he saw power lines and a ditch, which required him to change the helicopter’s flightpath and land on the far side of the ditch. He flared the helicopter about 100 ft above ground level, and the rotor speed began to decay rapidly. [T]he helicopter landed right skid low and then skidded for about 100 ft. The main rotor blades hit the ground as the helicopter rolled onto its right side. Safety Investigation The NTSB comment that the pilot’s recollection was consistent with a dual-engine loss of power and rotor system damage was consistent with no power at the time of impact. The fuel transfer system between the main tanks and the supply tanks and from the supply tanks to their respective engines and the fuel delivery system functioned normally during operational testing. No residual fuel was found within the engine fuel filter bowl, indicative of no fuel reaching the engines. Based on the pilot’s statement that he saw a steady stream of fuel leaking from a fuel vent port on the helicopter’s belly shortly after the accident, fuel was likely present within the main fuel tanks. Therefore, based on the evidence, it is likely that the pilot did not activate the fuel transfer pumps, which resulted in no fuel transferring between the main fuel tanks and the supply tanks and led to eventual fuel starvation. Thus, when the engines consumed all available fuel from their respective supply tanks, the dual-engine loss of power occurred. The helicopter’s warning and caution annunciator panel functioned normally during post-accident testing. However, it was found that the dimming function was activated. The pilot confirmed he had activated this feature before take-off. The annunciator panel contains caution lights for when the fuel transfer pumps are off and for when the fuel quantity in each supply tank is low. Illumination of these caution lights leads to the illumination of the master warning light but generates no aural tones. A night vision goggle (NVG) compatible...
read moreHelicopter External Sling Load Operation Occurrences in New Zealand
HESLO (Under Slung Load) Occurrences in New Zealand Data issued by the NZ Helicopter Association and NZ CAA show a rising trend in reported occurrences in NZ relating to external load operations and equipment. Around 60% of the reports relate to HESLO equipment or its rigging and about 35% relate to operations with a load. The report mentions UK CAA CAP426 Helicopter External Load Operations from 2006 as a safety resource. CASA issued Airworthiness Bulletin 25-006 “to notify operators and maintainers of additional safety information and current design standards for cargo hooks installed in helicopters”. It discusses phenomena such as Dynamic Rollout (or Ring Reversal), Jammed Loads / Hooks, Uncommanded Release / Inadvertent Cargo Hook Opening etc. Other Safety Resources Keep Your Eyes on the Hook! Underslung External Load Safety EC120 Underslung Load Accident 26 September 2013 – Report Unexpected Load: AS350B3 USL / External Cargo Accident in Norway Unexpected Load: B407 USL / External Cargo Accident in PNG Load Lost Due to Misrigged Under Slung Load Control Cable Fallacy of ‘Training Out’ Error: Japanese AS332L1 Dropped Load UPDATE 28 June 2020: Maintenance Issues in Fire-Fighting S-61A Accident Also: the UK AAIB report on a fatal accident to AS350B2 G-PLMH during HESLO with a boat at Loch Scadavay, Western Isles, Scotland, 13 June 2018, was issued in July 2019. Aerossurance has extensive air safety, operations, HESLO, airworthiness, human factors, aviation regulation and safety analysis experience. For practical aviation advice you can trust, contact us at: enquiries@aerossurance.com Follow us on LinkedIn and on Twitter @Aerossurance for our latest...
read moreFatal Taiwanese Night SAR Mission
Fatal Taiwanese Night SAR Hoist Mission (NASC AS365N3 NA-106) On 5 December 2018, a National Airborne Service Corps (NASC) Airbus Helicopters AS365N3 Dauphin NA-106, was carrying out a Search and Rescue (SAR) mission to hoist aboard an injured sailor from the bulk carrier W-STAR about 11 nm west of the Peng-Jia Islet when a winchman and patient were both fatally injured (in NASC’s second fatal hoisting accident in 31 days). Taiwan Transportation Safety Board (TTSB), which recently replaced the Aviation Safety Council (ASC) of Taiwan, issued their safety investigation report on 19 November 2019 (only available in full in Chinese). History of the Flight The flight was tasked in daylight. Sunset was 17:03, and civil twilight ended at 17:27. The winchman was lowered to pick up the casualty at around 17:45. While hoisting, the helicopter, which was not equipped with an autohover capability and so unsuitable for might hoisting, started to climb and accelerate. The hoist cable however snagged on the right landing gear. The photographs in the report do not show any hoist cable guard modifications. The flight crew decided to reduce speed and descend. They tried to hover over the sea and dipping the personnel on the hoist into the water to release the tension. The helicopter then continued to fly away from the ship. The TTSB say the crew was unable to maintain visual contact with the hoist and sea surface due to the low ambient light. The helicopter descended and then climbed twice without noticeable hovering operations over the sea. TTSB determined that the personnel on the hoist hit the water twice at a ground speed of 67 to 45 knots and then 37 to 17 knots in the red zone below). The winchman… …suffered from shock and lapsed into a coma while being pulled into the cabin. …organ injuries and serious fractures were also observed, indicating the presence of intense impact force when dipping into the water. Cable damage was found in several places on the fuselage. TTSB Analysis The tasking came about 1 hour before the end of evening twilight, but… …attempts to abort the mission did not succeed since the crew did not effectively evaluate and communicate the approach of the end of evening twilight and the possible unexpected situation beforehand. In addition, the flight crew unable to contact the on-boarded coast guard by radio, thus continued the hoist operation after the end of evening twilight and increased the risks of mission. There were neither written restriction served to limit the AS365N helicopter conducting SAR during the night, nor requirement to ask the flight crew abort sea hoist operation after the end of evening twilight… This… …led to the flight crew’s attempts to keep on trying the sea hoist operation…because of a sense of duty and commitment…and increased the risks of mission. TTSB say: NASC did not specify reasonable operation time prior to the end of evening twilight for those aircraft [that were daytime only capable] and did not develop a mechanism of risk control that authorises its command centre to deploy appropriate aircraft from other regions or hand over to the Taipei Rescue Coordination Centre for reinforcement. As the helicopter arrived target area and the winchman was lowered on deck, the preparations on board for hoist operation were not ready yet with the patient still inside the cabin, caused the delays and extended the operation time. TTSB Safety Recommendations To National Airborne Service Corps, Ministry of the Interior: Review aircraft dispatch related rules for explicitly defining written...
read more
Recent Comments