ARFF (Airport Rescue and Fire Fighting)

Today in History

ARFF Working Group - Wed, 07/03/2019 - 09:02

31 Years ago today: On 3 July 1988 an Iran Air Airbus A300B2-203 crashed into the Strait of Hormuz after being shot down by the USS Vincennes, killing all 290 occupants.

Date: Sunday 3 July 1988 Time: 10:24 Type: Airbus A300B2-203 Operator: Iran Air Registration: EP-IBU C/n / msn: 186 First flight: 1982-03-16 (6 years 4 months) Total airframe hrs: 11497 Engines:General Electric CF6-50C2 Crew: Fatalities: 16 / Occupants: 16 Passengers: Fatalities: 274 / Occupants: 274 Total: Fatalities: 290 / Occupants: 290 Aircraft damage: Destroyed Aircraft fate: Written off (damaged beyond repair) Location: 4 km (2.5 mls) SE off Qeshm Island (   Iran) Phase: En route (ENR) Nature: International Scheduled Passenger Departure airport: Bandar Abbas Airport (BND/OIKB), Iran Destination airport: Dubai Airport (DXB/OMDB), United Arab Emirates Flightnumber: IR655

Flight IR451 arrived at Bandar Abbas (BND) from Tehran (THR) at 08:40. The Airbus A300 was to continue to Dubai (DXB) as flight IR655. Prior to departure the crew received an enroute clearance to Dubai via the flight planned route A59 and A59W at FL140. The flight took off from runway 21 at 10:17 hours and climbed straight ahead.
Two minutes later, the crew reported leaving 3500 feet for FL140 on Airway A59, estimating MOBET at 06:53 UTC (10:23 Iran time). At 10:24:00 the aircraft passed MOBET out of FL120. At 10:24:43 two Airbus was hit by surface-to-air missiles. The tail and one wing broke off as a result of the explosions. Control was lost and the aircraft crashed into the sea.
The missiles were fired by the US Navy cruiser USS Vincennes. It was operating in the area together with the frigates USS Elmer Montgommery and USS John H. Sides. They were to protect other ships in the area.
At about the time the Airbus took off, the radar aboard the USS Vincennes picked up a brief IFF mode 2 response, which led to the mistaken identification of the Airbus as a hostile F-14 aircraft. The USS Vincennes issued 7 challenges on the Military Air Distress (MAD) frequency 243 MHz, addressed to ‘Iranian aircraft’, ‘Iranian fighter’ or ‘Iranian F-14’. These messages were followed by three challenges on the IAD (International Air Defence) radio frequency.
Due to increasing tension in the area – on May 17, 1987 an Iraqi Mirage had attacked USS Stark – all aircraft in the area had to monitor 121.5 Mhz: the International Air Defence – IAD radio frequency. There was no response.
Meanwhile radar operators were monitoring the Aegis screens. They reported that the incoming plane was descending with an increasing speed. In fact, the Airbus was climbing. Considering itself and USS Montgomery under aggression, USS Vincennes took the ultimate decision to launch missiles against the perceived hostile target at 10:24:22.
It remains uncertain whether the IR655 flight crew (only able to monitor the IAD, not the MAD frequencies) would have been able to rapidly identify their flight as the subject of the challenges made by the USS Vincennes

Probable Cause:

CAUSES: “The aircraft was perceived as a military aircraft with hostile intentions and was destroyed by two surface-to-air missiles.”

The post Today in History appeared first on ARFFWG | ARFF Working Group.

Today is Tuesday the 2nd of July, 2019

ARFF Working Group - Tue, 07/02/2019 - 06:11

Here are the stories for today…

Be safe out there!


The post Today is Tuesday the 2nd of July, 2019 appeared first on ARFFWG | ARFF Working Group.

Two confirmed dead after aircraft crash near Ephraim in Sanpete County

ARFF Working Group - Tue, 07/02/2019 - 06:09

By Laura Withers

SANPETE COUNTY, Utah, July 1, 2019 (Gephardt Daily) — A small aircraft crashed Monday afternoon east of Ephraim in the foothills of Bald Mountain.

Late Monday night, the Sanpete County Sheriff’s Office confirmed there were no survivors.

Detective Derick Taysom said Sanpete County Dispatch received a 911 call notifying them that a group of OHV operators had found the downed plane, and reporting that the aircraft’s two occupants were deceased.

The crash was approximately four miles northeast of Ephraim.

The sheriff’s office, Sanpete County Search and Rescue, and the Medical Examiner’s Officer went to the scene, and the pilot and passenger, both male, were confirmed deceased. The aircraft was identified as a “small glider-type of aircraft.”

In the course of the investigation, officials learned that the aircraft had taken off from the Nephi airport and was heading to an airport near Richfield.

Taysom told Gephardt Daily the names of the deceased are not being released pending notification of family.

The cause of the crash is unknown at this time. The Federal Aviation Administration will conduct an investigation Tuesday, Taysom said.

This was the second fatal crash of an aircraft in Utah since the weekend. A single-engine two-seat aircraft carrying the pilot and a passenger was reported missing Sunday and was found Monday morning in San Juan County. The two men on board were confirmed deceased.

Gephardt Daily will update this developing story as more information is made available.

The post Two confirmed dead after aircraft crash near Ephraim in Sanpete County appeared first on ARFFWG | ARFF Working Group.

Small plane crashes in Crawford County

ARFF Working Group - Tue, 07/02/2019 - 06:07

CRAWFORD COUNTY, Ark. (KNWA)- A small plane crashed on Highway 59 Monday afternoon. 

According to Crawford County Sheriff Ron Brown, a single-engine Beech A23 plane crashed just south of Van Buren at Hollis Lake Road and Highway 59.

An 18-year woman was taking a flying lesson with an instructor. Around 2,000 feet they lost all engine power.

After failed attempts to restart the engine, they made an emergency landing on the highway. The instructor took over and crash landed on Highway 59.

After he touched down, 50 feet later, the plane crashed into the ditch.

The plane is registered to BAP Group LLC of Fort Smith.

No one was injured as a result of the crash, according to Sheriff Brown.

Arkansas State Police are investigating along with the FAA.

The post Small plane crashes in Crawford County appeared first on ARFFWG | ARFF Working Group.

NTSB Reveals New Details in Deadly Plane Crash, Witness Recalls Tragedy

ARFF Working Group - Tue, 07/02/2019 - 06:05

By Maria Guerrero

The National Transportation Safety Board released new information related to Sunday morning’s plane crash that claimed the lives of 10 people, including two children.

During a press briefing, NTSB Vice Chairman Bruce Landsberg and lead investigator Dr. Jennifer Rodi said the twin engine Beechcraft BE 350 Super King airplane’s landing gear was down when it crashed into a hangar. 

“The airplane was airborne, so the airplane veered to the left, started to roll to the left, rolling when it collided with the hangar,” Landsberg said.

Rodi also revealed the entire plane made impact with the hangar, meaning it didn’t fall apart in the air.

Investigators said the hangar’s sprinkler system helped get the subsequent fire under control.

The NTSB also was able to recover the plane’s voice recorder. It captures communication between the pilots and their communication with air traffic control.

Landsberg said the “black box” is being analyzed in Washington D.C. but added as far as they know communication seemed “completely normal” that day. The small plane was cleared for takeoff, the pilots acknowledged.

Landsberg said there was, however, no flight data recorder device in the plane, which would have aided in the investigation.

Personal-use planes like the one involved in the deadly accident are not required to have them, although the NTSB has recommended it to the FAA, Landsberg said.

This means the NTSB will “take the long road” and rely heavily on the wreckage and especially on security video that captured the entire event.

Investigators have spoken with just a few people who witnessed the horrific crash, including a longtime local pilot.

David Snell was readying for his own flight Sunday morning to catch breakfast with friends when he witnessed the accident.

“My friend and I have flown for a long time,” he said. “We both knew that the sound that we were hearing out of that King Air was not correct.” 

Snell grabbed his cell phone and captured the horrific aftermath.

“It appears as though the airplane stalled and it fell to the left, and when that happens at a low altitude it’s impossible to recover,” he said.

Snell said he remembers hearing both engines running, but at a lower power setting.

“If you have a house fan: Speed one is low, speed four is high. When you’re taking off you should be at a three or four, and this sounded like it was at a one or a two,” he said. “But it didn’t sound like it was one engine operating at a high speed, like as if they lost one.”

According to Snell, the plane was simply too low and too slow on takeoff.

“Being a pilot, all of us can relate to incidents, accidents — we try to learn from them, but to see it happen in front of you and know that there’s a loss of life that’s going to take place and there’s not anything you can do about it, it’s pretty traumatic actually,” he said.

The NTSB is going to recover maintenance records for the aircraft; annual inspections are required.

The plane was two years old, according to the NTSB.

Investigators will also look at the pilot and his co-pilot’s training records. Pilots are required to have specific training to operate this specific aircraft.

A preliminary report is expected to be released by the NTSB in two weeks.

The post NTSB Reveals New Details in Deadly Plane Crash, Witness Recalls Tragedy appeared first on ARFFWG | ARFF Working Group.

FAA Reminds Travelers To Leave Fireworks At Home

ARFF Working Group - Tue, 07/02/2019 - 06:01

Cannot Be Carried On Airliners

As we celebrate Independence Day with family and friends, the FAA is asking everyone to keep safety front and center. 

While preparing your luggage for a flight, remember that fireworks are hazardous and are not allowed on aircraft. Fireworks are not allowed in carry-on baggage nor packed luggage. There are also other items that are used every day that are considered hazardous when brought on airplanes. For a Safe Start, Check the Chart!

And while you’re enjoying your drone during the holiday, know that it is not a great idea to try to capture firework activity with your drone.

There’s a new law ( that describes how, when, and where you can fly drones for recreational purposes.

Here are general guidelines for people flying drones:

  • Don’t fly your drone in or near fireworks
  • Don’t fly over people
  • Don’t fly near airports

To learn more about what you can and can’t do with your drone go to or download the B4UFLY app for free in the Apple and Google Play store.

Meanwhile, about those laser pointers…

It’s baffling but people actually point lasers at aircraft. That activity creates a serious safety risk to the pilot. It is illegal to shine lasers at aircraft and in many instances people can face federal charges.  Save yourself the legal trouble and lose the laser. If you witness someone aiming a laser at an aircraft, you’re encouraged to report the incident.

(Source: FAA. Image provided)


The post FAA Reminds Travelers To Leave Fireworks At Home appeared first on ARFFWG | ARFF Working Group.

Today in History

ARFF Working Group - Tue, 07/02/2019 - 05:59

25 Years ago today: On 2 July 1994 a USAir McDonnell Douglas DC-9-31 crashed at Charlotte following a windshear encounter; killing 37 out of 57 occupants.

Date: Saturday 2 July 1994 Time: 18:43 Type: McDonnell Douglas DC-9-31 Operator: USAir Registration: N954VJ C/n / msn: 47590/703 First flight: 1973 Total airframe hrs: 53917 Cycles: 63147 Engines:Pratt & Whitney JT8D-7B Crew: Fatalities: 0 / Occupants: 5 Passengers: Fatalities: 37 / Occupants: 52 Total: Fatalities: 37 / Occupants: 57 Aircraft damage: Destroyed Aircraft fate: Written off (damaged beyond repair) Location: Charlotte-Douglas Airport, NC (CLT) (   United States of America) Crash site elevation: 228 m (748 feet) amsl Phase: Approach (APR) Nature: Domestic Scheduled Passenger Departure airport: Columbia Metropolitan Airport, SC (CAE/KCAE), United States of America Destination airport: Charlotte-Douglas Airport, NC (CLT/KCLT), United States of America Flightnumber: 1016

USAir Flight 1016 was a domestic flight from Columbia (CAE) to Charlotte (CLT). The DC-9 departed the gate on schedule at 18:10. The first officer was performing the duties of the flying pilot.
The weather information provided to the flightcrew from USAir dispatch indicated that the conditions at Charlotte were similar to those encountered when the crew had departed there approximately 1 hour earlier. The only noted exception was the report of scattered thunderstorms in the area.
Flight 1016 was airborne at 18:23 for the planned 35 minute flight. At 18:27, the captain of flight 1016 made initial contact with the Charlotte Terminal Radar Approach Control (TRACON) controller and advised that the flight was at 12,000 feet mean sea level (msl). The controller replied “USAir ten sixteen … expect runway one eight right.” Shortly afterward the controller issued a clearance to the flightcrew to descend to 10,000 feet. At 18:29, the first officer commented “there’s more rain than I thought there was … it’s startin …pretty good a minute ago … now it’s held up.” On their airborne weather radar the crew observed two cells, one located south and the second located east of the airport. The captain said “looks like that’s [rain] setting just off the edge of the airport.” One minute later, the captain contacted the controller and said “We’re showing uh little buildup here it uh looks like it’s sitting on the radial, we’d like to go about five degrees to the left to the …” The controller replied “How far ahead are you looking ten sixteen?” The captain responded “About fifteen miles.” The controller then replied “I’m going to turn you before you get there I’m going to turn you at about five miles northbound.” The captain acknowledged the transmission, and, at 18:33, the controller directed the crew to turn the aircraft to a heading of three six zero. One minute later the flightcrew was issued a clearance to descend to 6,000 feet, and shortly thereafter contacted the Final Radar West controller.
At 18:35 the Final Radar West controller transmitted “USAir ten sixteen … maintain four thousand runway one eight right.” The captain acknowledged the radio transmission and then stated to the first officer “approach brief.” The first officer responded “visual back up ILS.” Following the first officer’s response, the controller issued a clearance to flight 1016 to “…turn ten degrees right descend and maintain two thousand three hundred vectors visual approach runway one eight right.”
At 18:36, the Final Radar West controller radioed flight 1016 and said “I’ll tell you what USAir ten sixteen they got some rain just south of the field might be a little bit coming off north just expect the ILS now amend your altitude maintain three thousand.” At 18:37, the controller instructed flight 1016 to ”turn right heading zero niner zero.” At 18:38, the controller said “USAir ten sixteen turn right heading one seven zero four from SOPHE [the outer marker for runway 18R ILS] … cross SOPHE at or above three thousand cleared ILS one eight right approach.” As they were maneuvering the airplane from the base leg of the visual approach to final, both crew members had visual contact with the airport. The captain then contacted Charlotte Tower. The controller said “USAir ten sixteen … runway one eight right cleared to land following an F-K one hundred short final, previous arrival reported a smooth ride all the way down the final.” The pilot of the Fokker 100 in front also reported a “smooth ride”. About 18:36, a special weather observation was recorded, which included: … measured [cloud] ceiling 4,500 feet broken, visibility 6 miles, thunderstorm, light rainshower, haze, the temperature was 88 degrees Fahrenheit, the dewpoint was 67 degrees Fahrenheit, the wind was from 110 degrees at 16 knots …. This information was not broadcast until 1843; thus, the crew of flight 1016 did not receive the new ATIS.
At 18:40, the Tower controller said “USAir ten sixteen the wind is showing one zero zero at one nine.” This was followed a short time later by the controller saying “USAir ten sixteen wind now one one zero at two one.” Then the Tower controller radioed a wind shear warning “windshear alert northeast boundary wind one nine zero at one three.”
On finals the DC-9 entered an area of rainfall and at 18:41:58, the first officer commented “there’s, ooh, ten knots right there.” This was followed by the captain saying “OK, you’re plus twenty [knots] … take it around, go to the right.” A go around was initiated. The Tower controller noticed Flight 1016 going around “USAir ten sixteen understand you’re on the go sir, fly runway heading, climb and maintain three thousand.”
The first officer initially rotated the airplane to the proper 15 degrees nose-up attitude during the missed approach. However, the thrust was set below the standard go-around EPR limit of 1.93, and the pitch attitude was reduced to 5 degrees nose down before the flightcrew recognized the dangerous situation. When the flaps were in transition from 40 to 15 degrees (about a 12-second cycle), the airplane encountered windshear. Although the DC-9 was equipped with an on-board windshear warning system, it did not activate for some unknown reason(s). The airplane stalled and impacted the ground at 18:42:35.

Investigation revealed that the headwind encountered by flight 1016 during the approach between 18:40:40 and 18:42:00 was between 10 and 20 knots. The initial wind component, a headwind, increased from approximately 30 knots at 18:42:00 to 35 knots at 18:42:15. The maximum calculated headwind occurred at 18:42:17, and was calculated at about 39 knots. The airplane struck the ground after transitioning from a headwind of approximately 35 knots, at 18:42:21, to a tailwind of 26 knots (a change of 61 knots), over a 14 second period

Probable Cause:

PROBABLE CAUSE: “1) the flight crew’s decision to continue an approach into severe convective activity that was conducive to a microburst; 2) the flight crew’s failure to recognize a windshear situation in a timely manner; 3) the flight crew’s failure to establish and maintain the proper airplane attitude and thrust setting necessary to escape the windshear; and 4) the lack of real-time adverse weather and windshear hazard information dissemination from air traffic control, all of which led to an encounter with and failure to escape from a microburst-induced windshear that was produced by a rapidly developing thunderstorm located at the approach end of runway 18R.

Contributing to the accident were: 1) the lack of air traffic control procedures that would have required the controller to display and issue ASR-9 radar weather information to the pilots of flight 1016; 2) the Charlotte tower supervisor’s failure to properly advise and ensure that all controllers were aware of and reporting the reduction in visibility and the RVR value information, and the low level windshear alerts that had occurred in multiple quadrants; 3) the inadequate remedial actions by USAir to ensure adherence to standard operating procedures; and 4) the inadequate software logic in the airplane’s windshear warning system that did not provide an alert upon entry into the windshear.”

The post Today in History appeared first on ARFFWG | ARFF Working Group.

Today is Monday the 1st of July, 2019

ARFF Working Group - Mon, 07/01/2019 - 10:21

After a busy weekend, we start the month of July with these stories…

Have a great week, be safe out there!


The post Today is Monday the 1st of July, 2019 appeared first on ARFFWG | ARFF Working Group.

2 escape injury when small plane catches fire shortly before landing in San Bernardino; firefighters extinguish flames

ARFF Working Group - Mon, 07/01/2019 - 10:17

By ERIC LICAS – Orange County Register

Fire broke out on a small plane shortly before its landing on a runway at San Bernardino International Airport on Sunday, June 30; and no one was reported injured after firefighters on the ground extinguished the flames.

Tower personnel notified authorities that the motor of a single-engine plane had caught fire as it came in for a landing on Runway 24 at about 5:27 p.m., San Bernardino County Fire Department spokesman Kyle Hauducoeur said. A crew stationed at the airport and specifically trained to extinguish burning aircraft doused it in fire retardant foam and water immediately after it landed.

A second team of firefighters was requested as backup, and the fire was out by 5:31 p.m., Hauducoeur said. The pilot and one passenger of the two-seater aircraft were unharmed, he said.

Information on what might have caused the fire was not immediately released.

The incident at San Bernardino International Airport was the second downed plane that San Bernardino County firefighters dealt with on Sunday. Earlier, another single-engine plane made an emergency landing within the boundaries of the Mojave National Preserve in Ludlow,  Hauducoeur said.

The post 2 escape injury when small plane catches fire shortly before landing in San Bernardino; firefighters extinguish flames appeared first on ARFFWG | ARFF Working Group.

10 dead after small plane crashes into Addison Airport hangar

ARFF Working Group - Mon, 07/01/2019 - 10:15

Written by Claire Z. Cardona, Dana Branham and Maria Elena Vizcaino

Updated at 9:55 p.m.: Revised to include information about who was on board the plane. 

All 10 people aboard a small plane died Sunday morning when it crashed into a hangar on takeoff at Addison Airport, authorities say. 

Two crew members and eight passengers were on board the twin-engine Beechcraft Super King Air 350 that was destroyed by flames after it crashed at 9:11 a.m., said Bruce Landsberg, vice chairman of the National Transportation Safety Board.

“We don’t know a lot about the people on board,” he said.

The flight had been headed to St. Petersburg, Fla. A Falcon jet and a helicopter that were inside the hangar were damaged, Landsberg said.

Addison spokeswoman Mary Rosenbleeth confirmed there were no survivors on the plane. The hangar was not occupied at the time of the crash.

The names of the people who died were not released while officials worked to notify their families, she said.

Addison fire spokesman Edward Martelle said the plane had just lifted off the runway when it veered left, dropped its left wing and went into the hangar.

The fire department had extinguished the fire and all hot spots at the hangar by 2 p.m.

The NTSB is leading the investigation into the crash. Officials offered no details about the cause and did not confirm whether engine failure to blame.

“We cannot confirm that there was engine failure at this point,” Landsberg said. “There are any number of possibilities that could occur and we’re not in a position to speculate on those kinds of things.” 

Jennifer Rodi, the NTSB’s lead investigator in the crash, said her team has walked through the scene several times to observe the wreckage.

The team will gather information on the flight crew on board — their training and knowledge — as well as details about how the plane was maintained and weather and communication factors that could have played into the crash.

The Federal Aviation Administration also sent investigators to the scene Sunday, FAA spokesman Lynn Lunsford said.

Martelle, the fire department spokesman, identified the plane’s registration number as N534FF. But he said authorities hadn’t confirmed who owned the plane and were looking into whether it recently had been sold.

A Chicago-area charter company had listed a King Air 350I with that registration number as part of its fleet, offering it as a nine-seat rental starting at $1,800 an hour. However, the aircraft was no longer available on the company’s website.

A search of the FAA registry did not turn up results for N534FF, but the plane’s serial number is also tied to another registration, which the FAA links to an Addison company.

The airport was closed for about 45 minutes after the crash before operations resumed.

Dallas County is helping the city of Addison set up a family assistance center for people affected by the crash, Judge Clay Jenkins said.

“It’s a very sad day for Dallas County,” he said. “My prayers are with the families we’re notifying about this tragedy.”

The mayor of St. Petersburg, Rick Kriseman, also expressed his condolences. 

“We are waiting on local officials in … [Texas] to release victim info,” he wrote on Facebook. “My thoughts are with the families of the deceased.”

David Snell, who said he was getting ready to fly from the airport, told KDFW-TV (Channel 4) he’d watched as the plane took off with what appeared to be reduced power.

“The plane started to veer to the left, and you could tell it couldn’t climb,” he said, adding that he could tell the plane was going to crash.

“That was really a horrific thing to see because somebody’s life, lives, family’s lives were forever changed. It’s awful,” Snell said.

Staff writers María Méndez and Sara Coello contributed to this report.

The post 10 dead after small plane crashes into Addison Airport hangar appeared first on ARFFWG | ARFF Working Group.

63-year-old man dead in single-engine plane crash near Elyria Airport

ARFF Working Group - Mon, 07/01/2019 - 10:07

By: Camryn Justice , Olivia Fecteau

ELYRIA, Ohio — Crews were called to Middle Avenue in Elyria after a single-engine plane crashed, killing the pilot, according to the Ohio State Highway Patrol. 

Around 2:30 p.m., OSHP responded to reports of a plane crash near the Elyria airport, troopers said.

The Lorain County Coroner was called to the crash for a 63-year-old man who was the pilot of the plane, according to LifeCare Ambulance.

The plane, a Piper Cub, was severely damaged and the pilot, later identified as Joseph E. Begany of Elyria, died from the injuries he sustained in the crash, troopers said.

Photos sent to News 5 by the homeowner of the property on which the plane crashed show the heavy damage.

No other injuries were reported, LifeCare Ambulance said.

Fellow pilots at Elyria Airport said they believe the pilot was based at a nearby airfield, Mole Airport, and came to Elyria Airport to get fuel.

The crash is currently under investigation and FAA investigators are on the way to the crash site.

The post 63-year-old man dead in single-engine plane crash near Elyria Airport appeared first on ARFFWG | ARFF Working Group.

Plane flying from LaGuardia to Houston makes emergency landing at Newark

ARFF Working Group - Mon, 07/01/2019 - 10:04

NEWARK, New Jersey (WABC) — An airplane flying from LaGuardia Airport to Houston, Texas, made an emergency landing at Newark International Airport after the plane experienced a brake problem, the FAA confirmed. 

United Airlines flight 2098, an Airbus A319, landed on Runway 22L around 8:46 a.m. Saturday, and the two left main tires blew when landing. The plane also experienced “other structural damage,” according to Port Authority.

Passengers were deplaned via slides, according to the FAA, but the number of passengers aboard the plane is unknown. They were taken by bus to Terminal C.

United spokesperson said in a statement that the plane experienced a “mechanical issue upon take-off.”

“Our pilots reacted quickly to ensure the safety of the aircraft and our customers,” the statement read.

At the time, all arrivals and departures were canceled but have since resumed, the airport tweeted. Travelers should expect delays.

The post Plane flying from LaGuardia to Houston makes emergency landing at Newark appeared first on ARFFWG | ARFF Working Group.

Troopers identify victims of plane crash near Moose Pass

ARFF Working Group - Mon, 07/01/2019 - 10:01

By Taylar Perez and Kristen Durand

ANCHORAGE, Alaska (KTUU) – Update (8:07 p.m.) –

Alaska State Troopers have tentatively identified the victims of the plane crash near Moose Pass. The bodies of the victims are not yet recovered, but believed to be the pilot, 73-year-old Michael Scott Christy and his wife, 69-year-old Jean Tam, both from Anchorage, along with 29-year-old Suzanne Glass from Sterling, Virginia.

Troopers say 28-year-old Andrea Joy Cooper is the sole survivor of the crash and is hospitalized in critical condition.

An Alaska State Trooper helicopter crew is expected to return to the crash site Sunday to retrieve the deceased victims.

Original story (12:08 p.m.) –

Three people are dead and one is seriously injured following a fatal plane crash near Moose Pass and Tern lake on Friday.

The National Transportation Safety Board public information officer Clint Johnson says they were notified of the crash around 6:00 p.m. Friday and currently have investigators in route.

Trooper dispatch reports that the aircraft’s Emergency Locator Transmitter was activated in mountainous terrain near mile 37 on the Seward Highway.

They confirm that the small plane was traveling with four people on board. The only survivor was rescued by Alaska Air National Guard Pararescuers who responded to the crash and transported the survivor to Providence ER in critical condition.

An Alaska State Trooper Helicopter will be flying in an attempt to recover the 3 other victims but recovery efforts are impeded because of the smoke from the nearby Swan Lake Fire.

The post Troopers identify victims of plane crash near Moose Pass appeared first on ARFFWG | ARFF Working Group.

Deadly medical helicopter crash in Brainerd ‘strikes us at the heart of what we do,’ sheriff says

ARFF Working Group - Mon, 07/01/2019 - 10:00

By Jennifer Kraus / Forum News Service

BRAINERD, Minn. — A North Memorial Air Care pilot and a nurse were killed following an early Friday morning helicopter crash in Brainerd.

Three North Memorial Health crew members, who, officials said worked in the Brainerd area, were on board when the helicopter crashed at 1 a.m. June 28 at Brainerd Lakes Regional Airport.

Crow Wing County Sheriff Scott Goddard said a pilot and a nurse were reported dead at the scene of the crash. A third crew member was transported to Essentia Health-St. Joseph’s Medical Center in Brainerd and their condition was unknown as of Friday afternoon.

Steve Wright, Brainerd airport director, said details on the helicopter’s flight information or what led to the crash was unknown. The Federal Aviation Administration and the National Transportation Safety Board were notified and are investigating the crash. Wright said the helicopter crashed in the middle of the airport, where the runways intersect.

“We have a lot of questions on this event that happened this morning,” Wright said later Friday morning. “We’re not sure if they were coming or going.

“We are a small airport community and we deal with these medical helicopters who are part of the emergency management system. So when our emergency responders respond to these types of events, it really hits close to home. These team members of the North Memorial crews and the other airport crews around here put their lives on the line for the community be safe. … We are asking for thoughts and prayers for these families and surviving members and those who are connected with these people who put their lives on the line day in and day out.”

Sheriff Goddard said, “Our hearts and prayers go out to all involved. We work with all our emergency service responders on a daily basis and everybody is one big, very close knit family and this strikes us at the heart of what we do. This is an unfortunate tragedy.”

The Crow Wing County Sheriff’s Office, along with the Brainerd police and fire department and the Baxter Police Department responded to the accident.

Wright said the airport will remain operational as the FAA and NTSB perform their investigations. The airport will still have its ribbon-cutting open house from 10:30 a.m. to 4 p.m. Saturday for its new general aviation terminal. The open house will feature speakers including local government leaders and a special appearance by Mark Baker, president of the Aircraft Owners and Pilots Association.

A prayer vigil for the victims of the crash is scheduled at 7 p.m. Sunday, June 30, at Whipple Beach Recreational Area in Baxter. In case of inclement weather, the vigil will be held under the shelter at the park.

The last known crash of a North Memorial Air Care helicopter was Sept. 16, 2016. The helicopter and its crew of three crashed near the edge of Lake Winona in Alexandria, about 86 miles southwest of Brainerd. All three Brainerd-based North Memorial crew members were hospitalized in critical condition at North Memorial in Robbinsdale.

A North Memorial spokesperson stated after the 2016 crash that it has been flying for more than 30 years and none of its helicopters have ever crashed. North Memorial owns Agusta helicopters, which fly at speeds up to 200 mph and are known to be the fastest civilian helicopters on the market.

North Memorial Air Care has bases in Brainerd, Bemidji, Princeton, Redwood Falls and Lakeville. North Memorial owns two hospitals in the Twin Cities metro area, including North Memorial Level 1 Medical Center in Robbinsdale, and has ground ambulance stations in Brainerd, Brooklyn Center and other cities throughout Minnesota and Wisconsin.

The post Deadly medical helicopter crash in Brainerd ‘strikes us at the heart of what we do,’ sheriff says appeared first on ARFFWG | ARFF Working Group.

KHP identifies man killed in plane crash near Hiawatha

ARFF Working Group - Mon, 07/01/2019 - 09:57


One person was killed Friday evening when a small plane crashed about a mile north of the Hiawatha airport in Brown Co.

According to the Brown Co. Sheriff’s Office, the plane went down around 5:30 p.m. in a cornfield, north of 260th Road, between Hwy. 73 and Mallard Rd.

Bruce L. Lutz, 67, of Andover, was declared dead at the scene. His body was transported to Frontier Forensics

Brown Co. Sheriff John Merchant said the Kansas Highway Patrol and FAA have been notified. He also complimented the various emergency response teams who arrived on the scene.

The post KHP identifies man killed in plane crash near Hiawatha appeared first on ARFFWG | ARFF Working Group.

Three injured in helicopter crash in Tucker County

ARFF Working Group - Mon, 07/01/2019 - 09:56

by: Alex Hines

UPDATE 06/29/19 9:41 p.m.: The helicopter that crashed in the Cheat River in Tucker County around noon Saturday has been recovered for further investigation by the Federal Aviation Administration.

West Virginia State Police troopers said a wire was found wrapped around the blades of the helicopter, and that it may have contributed to the crash.

The FAA has yet to determine the exact cause of the crash.

Authorities in Tucker County are investigating after a helicopter crashed there Saturday morning.

It happened around 11:30 on Saturday morning on Route 72 north of Parsons.

The West Virginia State Police say three people were in the helicopter when it crashed into the Cheat River near Licking Creek Road.

They say two have been airlifted to Ruby Memorial Hospital, and the third was transported on the ground.

No word yet on the nature of their injuries or the cause of the crash.

The post Three injured in helicopter crash in Tucker County appeared first on ARFFWG | ARFF Working Group.

Small plane flips after landing at Woodland Airport

ARFF Working Group - Mon, 07/01/2019 - 09:54

by: KOIN 6 News Staff

PORTLAND, Ore. (KOIN) — A small plane crashed Saturday morning after landing at the Woodland Airport.

Woodland Police said the 2-seat plane flipped onto its back after it had already landed and was taxiing on the runway. Authorities said the aircraft hit a depression in the runway, causing it to flip over.

No one was hurt.

The post Small plane flips after landing at Woodland Airport appeared first on ARFFWG | ARFF Working Group.

Project 31 – Reevaluation of Effectiveness of Emergency Vehicle Colors in Safety and Identification

ARFF Working Group - Fri, 06/28/2019 - 09:48

The color, lighting, and markings of Aircraft Rescue and Firefighting (ARFF) vehicles are critical to safe airport operation.  The FAA Advisory Circular AC 150/5210-5D states:  “Yellowish-green is the vehicle color standard.” However, recently the age of this AC has led to questions regarding whether it needs to be re-evaluated in accordance with recent advances in color schemes, paint materials, retroreflective materials, and lighting packages. The resulting FAA-sponsored project is being undertaken cooperatively by Ohio State University, Iowa State University, and Texas A&M University.  The attached PDF provides more context and describes initial progress.  The group would also like extensive feedback from practitioners who have experience in this area.  To achieve this, a survey has been developed to record the broadest possible range of specific experiences with this color while also establishing user perceptions regarding how the AC might be modernized.

You can find the survey at

FAA Annual Meeting_Project 31_2019_for ARFF WG_r

Link on the above link to view the FAA Annual Meeting Project 31 2019


The post Project 31 – Reevaluation of Effectiveness of Emergency Vehicle Colors in Safety and Identification appeared first on ARFFWG | ARFF Working Group.

Today is Friday the 28th of June, 2019

ARFF Working Group - Fri, 06/28/2019 - 06:16

We close out both the week and the month with the following stories…

Have a great weekend and be safe out there!


The post Today is Friday the 28th of June, 2019 appeared first on ARFFWG | ARFF Working Group.

Cessna plane crashes at Parkland Airport west of Edmonton

ARFF Working Group - Fri, 06/28/2019 - 06:14

By Karen Bartko

A Cessna plane crashed at a small regional airport west of Edmonton Thursday morning, flipping on its roof.

RCMP said the crash happened at 8:44 a.m. at the Parkland Airport (CPL6), located southeast of Spruce Grove near the Enoch Cree First Nation. 

The plane came to a rest upside-down on the runway, surrounded by emergency vehicles, including police, ambulances and fire trucks.

The Transportation Safety Board said a Cessna 140 with two people inside was landing when it “nosed over,” which the TSB said is similar to a vehicle getting into a fender bender.

AHS said it assessed the two men in the plane but they weren’t injured.

RCMP said no fuel leaked from the overturned plane, however the runway was temporarily closed and planes were being diverted 30 kilometres north to the Villeneuve Airport.

The airport is home to the Edmonton Flying Club. Private and recreational pilots also fly out of the single-runway airstrip.

Gerald Morgan, manager of the flying club, said it wasn’t their plane involved in the crash, but they helped to move the aircraft off the runway.

Morgan said both people in the plane were fine, and the runway reopened around 11 a.m.

Another resident said she was told by RCMP that a flying student was landing when the plane flipped on the runway.

The Transportation Safety Board said it would be following up on some details, but no formal investigation would be launched due to the minor nature of the crash.

The post Cessna plane crashes at Parkland Airport west of Edmonton appeared first on ARFFWG | ARFF Working Group.


Subscribe to Volunteer Mobile Emergency Response Unit -- aggregator - ARFF (Airport Rescue and Fire Fighting)