# NTSB ERA13LA134: Eurocopter Deutschland MBB-BK 117 C-2, N481LF, Danville, PA, February 14, 2013

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: February 14, 2013, 12:21 local (17:21 UTC)
- Place: Danville, PA
- Coordinates: 40.967777, -76.605552 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=40.9678&lon=-76.6056&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report November 13, 2014
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: BFU, FAA/FSDO, Geisinger Health Systems - Life Flight, BEA
- NTSB case key (mKey): 86230
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA13LA134
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86230/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86230
- Page: https://openairdocs.org/ntsb/ERA13LA134

## Probable cause

The pilot’s decision to conduct a straight-in approach to the helipad, which resulted in the main rotor blade impacting a construction crane flag marker. Contributing to the accident was the erroneous information about the construction crane’s operation time and the pilot’s self-induced time pressure, which resulted from his awareness of the patient’s medical situation during the flight.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Planning/preparation: flight planning/navigation](https://openairdocs.org/ntsb-findings/02061025): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-findings/02061025/cases.md?model=5626002), [All aircraft, 179 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=5626002), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Attention/monitoring: task monitoring/vigilance](https://openairdocs.org/ntsb-findings/02021520): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-findings/02021520/cases.md?model=5626002), [All aircraft, 330 cases](https://openairdocs.org/ntsb-findings/02021520/cases.md)
- [Oversight](https://openairdocs.org/ntsb-findings/04032000): Organizational issues › Support/oversight/monitoring · Operator (probable cause); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-findings/04032000/cases.md?model=5626002), [All aircraft, 7 cases](https://openairdocs.org/ntsb-findings/04032000/cases.md)
- [Object/animal/substance: ground equipment](https://openairdocs.org/ntsb-findings/03022050): Environmental issues › Physical environment · Accuracy of related info (probable cause); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 2 cases](https://openairdocs.org/ntsb-findings/03022050/cases.md?model=5626002), [All aircraft, 52 cases](https://openairdocs.org/ntsb-findings/03022050/cases.md)
- [Personality/attitude: motivation/respond to pressure](https://openairdocs.org/ntsb-findings/02021025): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-findings/02021025/cases.md?model=5626002), [All aircraft, 53 cases](https://openairdocs.org/ntsb-findings/02021025/cases.md)
- [Light condition: glare](https://openairdocs.org/ntsb-findings/03036030): Environmental issues › Conditions/weather/phenomena · Effect on personnel; cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-findings/03036030/cases.md?model=5626002), [All aircraft, 109 cases](https://openairdocs.org/ntsb-findings/03036030/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Prior to flight: Preflight or dispatch event](https://openairdocs.org/ntsb-events/030); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-events/030/sequence.md?model=5626002), [All aircraft, 355 cases](https://openairdocs.org/ntsb-events/030/sequence.md)
- [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Eurocopter Deutschland MBB-BK 117 C-2, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=5626002), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md)

## Analysis

The pilot reported that, as the helicopter approached mountainous terrain near the hospital during a helicopter emergency medical services (HEMS) flight, he turned the helicopter slightly right to pass through a gap in the ridgeline and then continued to fly directly to the heliport. The pilot then radioed that he was "3 minutes out." About this time, the medical crew intubated the patient, and the communications center advised the pilot that two people were on the roof to assist him. He then observed two individuals on the rooftop helipad, which, "while not abnormal," was "not routine." He was "a bit concerned" because he wanted to make sure the personnel were clear of the helipad before landing. The pilot recalled that he was somewhat more attuned to the patient's condition because the medical crew was working hard to keep the patient alive and was moving around the cabin unrestrained. He continued descending the helicopter on a straight-in approach and began the final approach to the rooftop helipad. About 100 yards from touchdown, he noticed something "orange" out of the left window. At almost the same time, the flight paramedic mentioned that he also "saw something orange." The pilot then felt a "slight low frequency vibration," which was also noticed by the flight nurse. About 6 seconds later, he landed the helicopter on the helipad, executed an emergency shutdown, and then cleared the crew to exit. A contractor who was operating a construction crane near the heliport reported that he was lowering a piece of equipment onto the roof of a building when he observed a helicopter approaching. Another contractor then observed one of the helicopter's blades contact the flag marker, which was mounted on the top of the construction crane boom, and "pieces of wood and flag…flying all over the place." Examination of the helicopter confirmed that the main rotor had contacted the flag marker and that one of its blades was substantially damaged. According to the pilot, neither he, the flight nurse, nor the flight paramedic had seen the construction crane before the helicopter contacted it while approaching the helipad. Review of photographs taken after the accident revealed that the pilot's straight-in approach to the rooftop helipad passed over the location of the construction crane, which was positioned next to a nearby building. Flight crews had been notified of the construction crane's position 2 days before the accident, and the pilot believed that he had briefed the crew about the presence of the construction crane at the medical center. According to the notification, the crane was to be in position between about 0700 to 1000 local time and was going to have a beacon on top because of the proximity of the helipad. However, no beacon was installed, and the crane was still in use and in position 2 hours 21 minutes after the notification advised that the work was supposed to be completed. No evidence was found indicating that the continued operationof the construction crane nor its presence was transmitted to the flight crewmembers when the flight was approaching the hospital. The investigation revealed that the communications technician was on the rooftop helipad at the time of the accident, not at her duty station manning the radio. The investigation also revealed that another helipad, which was located at ground level and was not near the construction crane, was available at the time of the accident and could have been used for the landing. If the pilot had been provided with correct information about the construction crane's operation time and its presence or if he had used the available ground-level helipad, he would have been more likely to have avoided the crane. However, if the pilot had followed the guidance in the company's general operations manual, which required that a high-orbiting reconnaissance be completed before beginning the approach and that all published helicopter procedures for the heliport and helipad be observed (which in the case of the rooftop helipad designated a left traffic pattern), the accident could have been prevented. Instead, the pilot flew a straight-in approach, which placed the helicopter's flightpath near the construction crane, restricted his ability to see due to sun glare, and placed the helicopter in a position that obstructed his view of the construction crane, which would have been behind the instrument panel as the helicopter approached the rooftop helipad. The National Transportation Safety Board has previously cited time pressure as a risk factor in HEMS flights. Due to the patient's critical condition, the pilot likely felt a sense of urgency to land, which influenced his decision to fly a straight-in approach to the rooftop helipad rather than to conduct a high-orbiting reconnaissance before initiating the approach. Although attempts are generally made to isolate HEMS pilots from the patient's condition while making go/no-go decisions, once onboard, it is difficult for pilots to be unaware of serious medical conditions that may be time critical, which leads to self-induced time pressures.

## Factual narrative

In order to improve safety, Geisinger Medical Center took the following actions: 1. In the event there is a crane in the vicinity of the hospital they would acquire multiple images of the crane from different angles to confirm location, angle, and exact height. 2. If a crane was placed in the direct path of flight to the rooftop helipad, the helipad would be temporarily closed. All incoming flights would land at the secondary helipad and patients would be transported to the Emergency Room via ground transportation. 3. To be sure the flight crews were aware of changes or notices, they will require an email confirmation that the flight crew has received the notice and that they have read and understood it. 4. Shift change and briefing reports will have stronger emphasis placed on discussing every detail with the oncoming crew during shift changes. 5. They will ensure that the communications center is fully staffed and that no Communications Technician is on the roof top helipad off-loading patients. 6. Communications Technicians will announce advisory hazards not only for takeoffs but during approaches as well, and the announcements will be made over one program-wide frequency, rather than a separate frequency for a particular helipad. 7. Required all pilots, flight paramedics, nurses and physicians, communication technicians, maintenance technicians, managers and support staff to participate in Air Medical Resource Management (AMRM) training to enhance the safety culture by promoting group cohesiveness and adaptation during change. 8. Created a Safety Manager position to develop and organize programs that support operational excellence, prevent accidents and incidents, and manage risk. The accident aircraft was a twin-engine medium utility–transport helicopter of conventional construction, configured for emergency medical use. It utilized a four-bladed main rotor with a hingeless rotor system, fiber-reinforced plastic blades, and a semi-rigid, two bladed tail rotor. It was powered by two turboshaft engines each producing 708 shaft horsepower. According to FAA and maintenance records, the helicopter was manufactured in 2010. The helicopter's most recent continuous airworthiness inspection was completed on January 10, 2013. At the time of the inspection, the helicopter had accrued 635.6 total hours of operation. Two heliports were located at Geisinger Medical Center. The first heliport (49PN) was located at ground level and was designated by the medical center as Helipad H1. It was a circular asphalt helipad, 46 feet in diameter, equipped with perimeter lights. The second heliport (79PN) was located on the roof of the hospital and was designated by the medical center as Helipad H2. It was 60 feet long by 50 feet wide, rectangular shaped, aluminum surfaced helipad. A left hand traffic pattern was designated for both heliports. On February 14, 2013, about 1221 eastern standard time, a Eurocopter MBB-BK-117 C-2, N481LF, operated by Geisinger MedicalCenter, doing business as Life Flight, was substantially damaged when the main rotor contacted a flag marker, mounted on a construction crane, during approach, at Geisinger Rooftop Heliport (79PN), Danville, Pennsylvania. The pilot, flight nurse, flight paramedic, and patient were uninjured. Visual meteorological conditions prevailed for the Title14 Code of Federal Regulations (CFR) Part 135 helicopter emergency medical services (HEMS) flight, which originated at Muncy Valley Hospital Heliport (7PS5), Muncy, Pennsylvania at 1210. According to the pilot, they departed their base at Primrose Heliport (25PS), Minersville, Pennsylvania for 7PS5 to pick up a patient for an interfacility transfer. After arriving at 7PS5 at 1142, the patient was loaded and they departed for 79PN at 1212. The patient was "doing poorly" and there was some initial consideration as to whether the patient was alive and whether to fly him at all. After departure, the pilot climbed to 2000 feet above mean sea level (msl) and flew on an approximate 160 degree magnetic heading, direct to 79PN. As the helicopter approached the mountains near Danville the pilot turned slightly right to pass through a gap in the ridgeline and continued to fly direct to the heliport. The pilot then radioed in that he was "3 minutes out." Around this time the medical team intubated the patient, and he was advised by the communications center that there were two people on the roof to assist him. He then observed two individuals on the rooftop landing pad, which "while not abnormal" was "not routine". He was "a bit concerned" as he wanted to make sure the personnel were clear of the helipad prior to him getting any closer. The pilot recalled that he was somewhat more attuned to the patient's condition as the medical crew was working hard to keep the patient alive and were moving about the cabin unrestrained. He continued descending, and commenced his final approach to the rooftop helipad. About 100 yards from touchdown he noticed something "orange" out of the left window. At almost the same time the flight paramedic mentioned that he "saw something orange". The pilot then felt a "slight low frequency vibration". This vibration was also noticed by the flight nurse. About 6 seconds later, he landed on the landing pad, executed an emergency shutdown, and then cleared the crew to exit. According to contractors who were operating a construction crane near the heliport, they were lowering a piece of equipment onto the roof of a building when one of them observed a helicopter approaching. Another one of the contractors then observed that "all of a sudden." He saw one of the blades of the helicopter hit the safety flag (flag marker) which was mounted on the top of the construction crane boom, and "pieces of wood and flag were flying all over the place." At this point, the contractors stopped all operations with the construction crane, to confirm that all of their personnel were uninjured, and to insure thatthe boom and cable did not receive any damage. The reported weather at Penn Valley Airport (SEG), Selinsgrove, Pennsylvania, located 15 nautical miles southwest of the accident site, at 1253, included: calm winds, 10 miles visibility, clear, temperature 04 degrees C, dew point -03 degrees C, and an altimeter setting of 29.96 inches of mercury. Life Flight started in 1981 as a HEMS operation providing critically ill or injured patients rapid access to advanced life support, and transportation to critical care facilities. Life Flight operated 24 hours a day from 5 bases averaging 2,600 flights per year. They initially operated under contracted air carrier certificates. In 2012, they were issued their own Title 14 CFR Part 135 air carrier certificate. At the time of the accident, they operated 6 helicopters, each of which was equipped with a night vision system, traffic collision avoidance system, and terrain avoidance system operating in both visual meteorological conditions and instrument meteorological conditions. During inclement weather they would utilize instrument flight rules to continue operations in adverse weather conditions including rain, snow, and decreased visibility. Normal cruising Altitude for the life flight program was between 3,000 and 5,000 feet above mean sea level. In addition to emergency response, Life Flight also transported premature newborns, cardiac patients, critical care, and organ transplant patients. Life Flight helicopter crews consisted of a pilot, flight nurse, flight paramedic, and in certain circumstances, a flight physician or specialty nurse. All pilots were airline transport rated and instrument current. All communications specialists were emergency medical technicians and were experienced in emergency medical service and medical communications and were credentialed by the National Association of Air Medical Communications Specialists. Communications between the helicopters and hospitals was done through a wide range of radio frequencies and satellite telephone. Flight following consisted of monitoring using real time satellite tracking by a dispatch and operations center that was staffed by two Communications Technicians. According to Federal Aviation Administration (FAA) and pilot records, the pilot held an airline transport pilot certificate with ratings for rotorcraft-helicopter, commercial privileges for airplane single-engine land, airplane multiengine-land, and instrument airplane, and held type ratings for the SK-64 and SK-65. He also held a flight instructor certificate with ratings for rotorcraft-helicopter and instrument helicopter. His most recent FAA first-class medical certificate was issued on September 11, 2012. He reported 3,035 hours of total flight experience, 12 of which was in the accident helicopter make and model. Construction Crane Information Review of photographs taken after the accident revealed that the helicopter's final approach passed over the location of the constructioncrane which was positioned next to a building known as the "Annex" where it was being used to remove condensers from the roof. Interviews with the crane operator revealed that at time of the accident, the construction crane's boom had been inclined upward on a 66 degree angle and extended out 133 feet, and was aligned with the helicopter's flight path along its final approach. Flight crews had been notified of the construction crane's position on February 12, 2013. Prior to their departure from 25PS, the pilot believed that he had briefed his crew about the presence of the construction crane at the medical center. According to the notification, the crane was to be in position about 0700 to approximately 1000 and was going to have a beacon on top, because of the proximity of the helipad. However, no beacon was installed; the crane was in use, and still in position, 2 hours and 21 minutes after the notification advised that contractors removing the condensers from the roof were supposed to have completed their work. Communications Information According to the Geisinger Medical Center General Operations Manual (GOM), Maximum use of radio facilities would be made on all departures and arrivals. During the investigation it was determined however, that one of the people observed by the pilot on the rooftop helipad when the helicopter was inbound was the Communications Technician that would normally man the radio in what was known as the "Glass House" next to the helipad on the roof of the hospital. Helicopter Approach and Restrictions to Visibility According to the pilot, he approached the heliport from the north which was not the way they would usually come in to the helipad. They usually would approach from the south. Review of witness statements revealed that despite the prevailing visibility of 10 miles, the helicopters straight in flight path would have restricted the pilot's ability to see the construction crane as he would have been subject to sun glare, and as he approached the construction crane, it would have been below him at his 11 o'clock position as he approached the helipad. Examination of the cockpit layout also indicated that as he approached the construction crane, the crane would not have been in the pilot's direct line of sight, as his view of the construction crane and portions of the Annex roof would have been obstructed by the helicopter instrument panel. Approach Procedures According to the Geisinger Medical Center GOM (12.9.6 VFR Approach Procedures), visual flight reference (VFR) approaches and departures to and from approved heliports or helipads were required to be accomplished with great caution: 1. A high orbiting reconnaissance was required to be completed by the pilot prior to beginning the approach. 2. Pilots were required to use continued vigilance during all phases of approach and departure, searching for obstacles and debris in the landing zone. 3. Pilots were required to make maximum use of the prevailing windduring the approach and departure procedures while maneuvering to remain a safe distance from obstacles. 4. All published helicopter procedures for the heliport and helipad were supposed to be observed. Examination of Construction Crane Examination of the construction crane revealed that the metal pole that held the flag marker was damaged and the wooden pole that the flag marker was attached to was missing. Examination of Helicopter Examination of the helicopter confirmed that the main rotor had come into contact with the flag marker. Two blades; the Green Blade, and the Blue Blade of the four-bladed main rotor were damaged. The Green Blade incurred minor tip damage. The Blue Blade was substantially damaged and required replacement. According to the pilot neither he, the flight nurse, nor the flight paramedic, had seen the construction crane prior to coming into contact with it while approaching the landing pad.

## Aircraft

- Registration: [N481LF](https://openairdocs.org/aircraft/N481LF), registered now, S/N 9392, built 2010 (OpenAirDocs)
- Reported make and model: EUROCOPTER DEUTSCHLAND GMBH MBB-BK 117 C-2
- Registry model: [Eurocopter Deutschland MBB-BK 117 C-2](https://openairdocs.org/model/eurocopter-deutschland-mbb-bk-117-c-2) (registry code 5626002) (OpenAirDocs)
- Registry engine: [Turbomeca ARRIEL-1E2](https://openairdocs.org/engine/turbomeca-arriel-1e2) (registry code 60035, turbo-shaft) (OpenAirDocs)
- Category: Helicopter
- Serial number: 9392
- Year built: 2010
- Airframe hours: 636
- Engines: TURBOMECA ARRIEL 1E2 708 horsepower turbo shaft; TURBOMECA ARRIEL 1E2 708 horsepower turbo shaft
- Damage: Substantial damage
- Flight: Part 135
- Operator: Geisinger Medical Center, doing business as Life Flight
- Registered owner: Geisinger Medical Center
- Airworthiness certificate: Standard, Normal
- Last inspection: Continuous airworthiness, January 10, 2013
- Departed: 7PS5, Muncy, PA
- Destination: 79PN, Danville, PA
- Flight plan: Company VFR
- Airport: 79PN, Geisenger Rooftop Heliport, runway H2, 60 × 50 ft, metal/wood
- Equipment: Satellite tracking device, Auto-pilot

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 55; injuries: none; airline transport, commercial, flight instructor; airplane ratings: multi-engine land, single-engine land; instrument ratings: helicopter, airplane; medical: class 1, with waivers/limitations; last flight review January 14, 2013; seat: right; restraint: 4-point; flight hours: 3,035 total, 12 in this make and model, 2,310 as pilot in command, 40 in the last 90 days, 20 in the last 30 days, 2 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 36 °F, dew point 25 °F
- Altimeter: 29.97 inHg
- Observed at: SEG, 15 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20130214002389A](https://openairdocs.org/incident/20130214002389A), Feb 14, 2013: Eurocopter Deutschland Gmbh MBB-BK 117 C-2, Danville, PA, Minor damage. Pilot, two medical crewmembers and a patient were on final approach to 79PN when the main rotor blades made contact with a flag that was on top of a working…

## Docket (14 files)

The files NTSB released with the investigation on October 17, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86230. 8.0 MB in all.

- Three View Drawing – Courtesy of American Eurocopter (item 1, .PDF, 31 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417782&FileExtension=.PDF&FileName=Three%20View%20Drawing%20%E2%80%93%20Courtesy%20of%20American%20Eurocopter-Master.PDF
- Preaccident Image of N818LF – Courtesy of American Eurocopter (item 2, .PDF, 99 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417783&FileExtension=.PDF&FileName=Preaccident%20Image%20of%20N818LF%20%E2%80%93%20Courtesy%20of%20American%20Eurocopter-Master.PDF
- Simulated Image of View from Pilot’s Seat – Courtesy of American Eurocopter (11 O’Clock, Low View) (item 3, .PDF, 177 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417784&FileExtension=.PDF&FileName=Simulated%20Image%20of%20View%20from%20Pilot%E2%80%99s%20Seat%20%E2%80%93%20Courtesy%20of%20American%20Eurocopter%20(11%20O%E2%80%99Clock,%20Low%20View)-Master.PDF
- NTSB Form 6120 (item 4, .PDF, 779 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417785&FileExtension=.PDF&FileName=NTSB%20Form%206120-Redacted.PDF
- Witness Statements and Interview Summaries (item 5, .PDF, 920 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417786&FileExtension=.PDF&FileName=Witness%20Statements%20and%20Interview%20Summaries-Redacted.PDF
- Life Flight Base Locations – Courtesy of Geisinger Medical Center (item 6, .PDF, 159 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417787&FileExtension=.PDF&FileName=Life%20Flight%20Base%20Locations%20%E2%80%93%20Courtesy%20of%20Geisinger%20Medical%20Center-Master.PDF
- Maps and Charts of Accident Site – Aerial and Satellite Images (item 7, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417788&FileExtension=.PDF&FileName=Maps%20and%20Charts%20of%20Accident%20Site%20%E2%80%93%20Aerial%20and%20Satellite%20Images-Master.PDF
- Weather Reports and Records – KSEG METARs (item 8, .PDF, 51 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417789&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records%20%E2%80%93%20KSEG%20METARs-Master.PDF
- Damage to Helicopter and Crane – As Provided by Life Flight (Contains 10 Images) (item 9, .PDF, 4.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417791&FileExtension=.PDF&FileName=Damage%20to%20Helicopter%20and%20Crane%20%E2%80%93%20As%20Provided%20by%20Life%20Flight%20(Contains%2010%20Images)-Master.PDF
- Pilot’s GMC Form OP01 – Shift Change and Briefing Form (item 10, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417792&FileExtension=.PDF&FileName=Pilot%E2%80%99s%20GMC%20Form%20OP01%20%E2%80%93%20Shift%20Change%20and%20Briefing%20Form-Redacted.PDF
- Excerpts from GMC Form OP01 – Guidance (6.6.3 Inter-Facility Transfers) (item 11, .PDF, 160 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417793&FileExtension=.PDF&FileName=Excerpts%20from%20GMC%20Form%20OP01%20%E2%80%93%20Guidance%20(6.6.3%20Inter-Facility%20Transfers)-Master.PDF
- Excerpts from GMC Part 135 GOM – Crew Vigilance and VFR Approach Procedures (item 12, .PDF, 220 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417794&FileExtension=.PDF&FileName=Excerpts%20from%20GMC%20Part%20135%20GOM%20%E2%80%93%20Crew%20Vigilance%20and%20VFR%20Approach%20Procedures-Master.PDF
- Excerpts from GMC Part 135 GOM – Restriction or Suspension of Flights (item 13, .PDF, 49 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417795&FileExtension=.PDF&FileName=Excerpts%20from%20GMC%20Part%20135%20GOM%20%E2%80%93%20Restriction%20or%20Suspension%20of%20Flights-Master.PDF
- Statement of Party Representative to NTSB Investigation (item 14, .PDF, 114 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417796&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representative%20to%20NTSB%20Investigation-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.