Wednesday, November 11, 2015

Hospital: Drone delayed helicopter from picking up patient

 
EMS pilot Gary Colecchi 
 

FORT WORTH – Little Lucy James is one week old Wednesday. She arrived in this world nine weeks early, weighing just 3 lbs., 13 oz.

"She's not very big," says mom Alex James. "She doesn't know that. She thinks she's huge."

Holding and cuddling the little baby are magic moments for moms Alex and Katie James. But the moments leading up to Lucy's delivery were much more tense. Doctors in Decatur told the parents Lucy's lungs weren't fully developed, and she'd need to be flown immediately to Cook Children's Hospital in Fort Worth.

"It was really scary, honestly," Alex said.

"These kids need medical attention, and they need it rather fast," said EMS pilot Gary Colecchi, who flies for Cook Children's Teddy Bear Transport.

That's why an incident this summer at Cook Children's has pilots like Colecchi concerned.

Back in July, a medical chopper had just dropped off a patient.

"They were then dispatched to another critical injured child," Colecchi said. "However, they were unable to take off for 20 minutes because someone was flying a drone around [the] hospital."

That means a North Texas child had to wait 20 minutes longer than necessary for crucial medical attention, all because of a drone.

"It could've been bad," said Debbie Boudreaux, director of transportation for Cook Children's Hospital.

Boudreaux worries this is a sign of things to come, as drones pick up in popularity.

The FAA estimates at least 700,000 drones will be sold by the end of the holiday season. The issue is that, currently, the FAA has no laws on where you can fly drones. They simply suggest not to fly within five miles of airports, including hospital helicopter pads.

Actual laws should be coming soon, according to an FAA spokesperson.

In the meantime, Cook Children's and other hospitals are pleading for people not to fly drones near their facilities for fear the next 20-minute delay means the child doesn't get a happy ending, like Lucy James.

If you plan to fly a drone, first click here to see a website for guidance on where to fly safely.

- Source:  http://www.wfaa.com


Cessna 182Q Skylane, N96381, 96381 Inc: Fatal accident occurred November 10, 2015 in Richmond, Ray County, Missouri

The National Transportation Safety Board traveled to the scene of this accident. 

Additional Participating Entities: 
Federal Aviation Administration; Kansas City, Missouri
Continental Motors; Mobile, Alabama
Textron Aviation; Wichita, Kansas
Federal Aviation Administration; Olathe, Kansas
National Air Traffic Controllers Association; Houston, Texas

Aviation Accident Final Report - National Transportation Safety Board: https://app.ntsb.gov/pdf

Investigation Docket - National Transportation Safety Board: https://dms.ntsb.gov/pubdms

Aviation Accident Data Summary - National Transportation Safety Board: https://app.ntsb.gov/pdf

96381 Inc: http://registry.faa.gov/N96381

NTSB Identification: CEN16FA037
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 10, 2015 in Richmond, MO
Probable Cause Approval Date: 07/12/2017
Aircraft: CESSNA 182Q, registration: N96381
Injuries: 1 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

As the airplane neared the destination airport in dark night visual meteorological conditions at the conclusion of a cross-country flight, the private pilot reported a partial loss of engine power. The air traffic controller provided the pilot with a vector and information for the nearest airport, which, according to his display, was equipped with a lighted, grass runway. Although the airport was equipped with a rotating beacon and runway lighting, these lights could not be pilot-operated and required manual activation by the airport owner. This information was not available to the controller. In attempting to assist the pilot in restoring engine power, the pilot-rated controller suggested that the pilot turn off the carburetor heat. Eventually, radar contact with the airplane was lost, and the controller continued to provide vectors to the pilot while also attempting to obtain more information about the airport, including a common traffic advisory frequency to activate the lighting system. Radio contact was lost with the airplane about 7 minutes after the loss of radar contact.

The airplane impacted trees and terrain about 1 nautical mile from the diversionary airport. All of the engine’s spark plugs displayed carbon fouling, consistent with an overly rich fuel-air mixture. No other anomalies were detected with the airframe or engine that would have precluded normal operation. Although the airplane was operating in an area conducive to the formation of carburetor icing at glide power, it could not be determined if the engine experienced carburetor icing at the time the pilot reported that she had engine problems because she had the carburetor heat on and was likely operating at cruise power. Additionally, the effect of the controller’s suggestion to turn off the carburetor heat could not be determined.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The airplane's impact with trees and terrain during an off-airport forced landing in dark night conditions following a partial loss of engine power. The reason for the partial loss of engine power could not be determined because postaccident examination did not reveal any mechanical anomalies that would have precluded normal operation.

HISTORY OF FLIGHT

On November 10, 2015, about 1858 central standard time, a Cessna 182Q, N96381, impacted trees and terrain during an off-airport forced landing near Richmond, Missouri. The pilot was fatally injured and the airplane was substantially damaged. The airplane was registered to 96381 Inc., Ortonville, Michigan, and was operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Dark night visual meteorological conditions prevailed and no flight plan was filed. The airplane departed Oakland County International Airport (PTK), Pontiac, Michigan, about 1530 eastern standard time, and was destined for Charles B. Wheeler Downtown Airport (MKC), Kansas City, Missouri.

The pilot was receiving visual flight rules flight following services from air traffic control. At 1848:46 (all times are central standard time unless otherwise noted), about 40 nautical miles northwest of MKC, the pilot contacted the Kansas City International Airport departure east radar air traffic controller. The controller responded with the MKC landing runway information and advised the current Automatic Terminal Information Service code. The pilot replied that she had the current weather information.

At 1849:44 while heading approximately 245°, the pilot transmitted, "…I need some help." After the controller acknowledged, the pilot said, "I need an airport right now, I've lost a lot of my engine power, and I don't know why." The controller advised the pilot of an airport about 5 miles southwest of her position (Curtis Field Airport, 8MO3), provided a vector of 225°, and stated that the runway was 2,400 ft long and 80 ft wide and was lit. At 1850:21, the pilot acknowledged, but stated, "I think I'm turning the wrong way." In a subsequent transmission, the pilot stated, "I am just really nervous if you could help me please." The controller advised the pilot, who had turned the airplane northwest, to turn southwest, and the pilot acknowledged.

Shortly thereafter, the controller asked the pilot if the engine had "any power at all," to which the pilot replied, "…I have some power but it's just really reduced." The controller then asked the pilot if the airplane's pitot heat was on. The pilot replied that it was, and the controller advised the pilot to turn it off. The controller subsequently asked if the airplane's carburetor heat was on. The pilot confirmed that it was, and the controller advised the pilot to turn it off; the pilot replied, "Carb heat off."

At 1852:52, about 3 miles from 8MO3, the pilot stated to the controller that she did not have the airport or its beacon in sight. The controller instructed the pilot to continue southbound and described the runway. The pilot asked if the airport was lit and if the controller could, "…ask them to turn on the lights." The controller responded that it was an uncontrolled airport. The pilot advised that she did not have the airport's common traffic advisory frequency (CTAF), and the controller instructed her to stand by.

About 1854, the controller advised the pilot that radar contact had been lost. The pilot reported that the airplane was at 1,800 ft and that she did not have the airport in sight. The controller then stated that the airport was a "grass field," and asked, "is there still daylight out?" The pilot replied that she "could not see anything." The controller stated, "The closest airport with lighting and cement is Mosby Airport," but the controller did not provide a direction or distance to this airport. The pilot stated that the airplane was at 1,600 ft and losing altitude. The controller then provided the pilot a CTAF frequency of 122.9, which the pilot acknowledged.

At 1855:47, the controller stated to the pilot, "You need to start looking for the airport there if you can," and asked for the airplane's altitude. The pilot did not reply. About one minute later, the pilot stated, "I can't see at this point…[unintelligible] try again." There were no further communications from the pilot.

A witness, who was about two miles northwest of 8MO3, saw the navigation and landing lights of a southbound airplane. He reported that the airplane passed directly overhead about 500 ft above him and the engine sounded like it was "spitting." The airplane was more than one mile away, had completed a left turn, and was proceeding almost due west when the witness saw the airplane descend and disappear from sight. Shortly afterward, he heard two distinct "thuds." The witness immediately contacted emergency services, and the wreckage was subsequently located at 2126.

PERSONNEL INFORMATION

A review of the pilot's logbook found flight entries from 2002 until December 6, 2014. No additional logbook was located. Using the pilot's logbook, airplane logs, and interviews with the pilot's family and friends, the pilot's total flight experience was estimated to be 744 total hours, of which 119 hours was in the Cessna 182 variants, 109 hours of night time, and 38 hours of simulated instrument conditions. The pilot's last recorded flight review was dated August 10, 2011. Although the pilot completed the necessary requirements on August 15, 2013, she did not request a flight review endorsement from the instructor, so no endorsement was signed.

AIRCRAFT INFORMATION

The airplane's last inspection was a combined 100 hour/annual completed on October 2, 2015. At the time of the inspection, the airframe had accrued 2,214.8 hours, and the engine had 1,297.6 hours since major overhaul. The airplane was equipped with a Garmin GNS-430 GPS/NAV/COM radio which provided both navigation and communication capabilities. It could not be determined if the pilot routinely operated the GNS-430.

METEOROLOGICAL INFORMATION

Data from the U. S. Naval Observatory showed that moonset occurred at 1650, sunset occurred at 1706, and the end of evening civil twilight occurred at 1734.

A review of the Carburetor Icing Probability Chart located in FAA Special Airworthiness Information Bulletin CE-09-35 revealed that the airplane was operating in an environment conducive to the formation of serious icing at glide power settings.

AIRPORT INFORMATION

The diversion airport provided to the pilot by air traffic control was Curtis Field Airport (8MO3), a private use airport located about 3 miles northeast of Richmond, Missouri. The airport was not equipped with a control tower and was attended only during daylight hours. Runway 17/35, a lighted turf runway, was 2,500 ft long and 80 ft wide. Although the airport was equipped with a rotating beacon and runway lighting, it could not be pilot-activated; airport personnel must be called at a phone number to manually turn the lighting on. At the time of the accident, the lights on the field were off.

WRECKAGE AND IMPACT INFORMATION

The airplane impacted trees and terrain about 1.28 nautical miles west of 8MO3. The initial impact point was identified by damage to an 80 ft tall tree. The airplane continued about 275 ft to an open field northwest of the initial impact point, and collided with the ground in an approximate 80° nose-low attitude. The airplane's propeller was found separated from the engine near the impact crater. The leading edges of both wings and the forward portion of the fuselage were crushed aft.

Flight control continuity was confirmed to all control surfaces. Elevator trim was found about 6-7° nose-down. All fuel filters and strainers were found clear of debris. The fuel selector was found in the right tank position, and the right tank contained about 11 gallons of fuel. Fuel was found in the sump bowl and the carburetor accelerator pump. The propeller blades were relatively undamaged. One blade was deformed rearward about 30° near its mid-span.

The engine was removed and sent to Continental Motors Analytical Department, Mobile, Alabama, for examination. Disassembly and examination of the engine revealed no mechanical defects with the engine. All twelve spark plugs were found fouled.

MEDICAL AND PATHOLOGICAL INFORMATION

The county coroner elected not to perform an autopsy on the pilot. Blood was drawn for toxicology testing.

The FAA Bioeraeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, performed forensic toxicology on blood specimens from the pilot. Testing was negative for carbon monoxide, ethanol, and all tested-for substances.

ADDITIONAL INFORMATION

Air Traffic Control Services

At the time that the pilot reported engine difficulty, 8MO3 was the nearest airfield, and was located about 5 miles southwest of the airplane's position. The next closest airports were an additional 7 miles away. The Standard Automation Replacement System (STARS) emergency airport function on the controller's displayed that 8MO3 was a lighted, grass runway, and no CTAF frequency was provided. He stated that the airplane was rapidly losing altitude, and he could tell that the pilot was very nervous. He also stated that it was daylight when he had been assigned the position, and he did not realize that it had become dark outside. The controller held a private pilot certificate with instrument rating, and stated that, while attempting to assist the pilot, he recalled his flight training and factors that may have an adverse effect on engine performance. He advised the pilot to turn the airplane's pitot heat off, then later realized that the use of pitot heat would not affect engine power. After discussions with another pilot-rated controller in the room, he advised the pilot to turn the engine's carburetor heat off. Another controller then provided him an incorrect CTAF frequency for a different airport, which he subsequently relayed to the pilot.

According to radar data, radar contact with the airplane was lost at 1851:39; however, the controller did not advise the pilot that radar contact had been lost until 1854:09. FAA Order 7110.65 stated that controllers are required to inform an aircraft of radar contact both when initial radar identification is established and when radar contact is lost. The order also stated that, in the event of an emergency, controllers are required to coordinate search and rescue (SAR) efforts. In order to facilitate SAR, controllers should gather pertinent information from the pilot, including estimated location and altitude, direction of flight, number of persons on board, and a description of the aircraft. The accident controller did not request this information.
After the accident occurred, the controller attempted to call 911, but was unable to dial outside of the facility. Eventually, a frontline manager was able to complete the call. The controller also reported that he did not think that he had not received adequate training to respond to emergency situations, and that the annual simulation training he received "always seemed to be on the same thing."

Pilot's Operating Handbook Information

The manufacturer's pilot's operating handbook for the airplane stated, "An unexplained drop in manifold pressure and eventual engine roughness may result from the formation of carburetor ice. To clear the ice, apply full throttle and pull carburetor heat knob full out until the engine runs smoothly; then remove carburetor heat and readjust the throttle. If conditions require the continued use of carburetor heat in cruise flight, use the minimum amount of heat necessary to prevent ice from forming and lean the mixture for the smoothest operation."

NTSB Identification: CEN16FA037 
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 10, 2015 in Richmond, MO
Aircraft: CESSNA 182Q, registration: N96381
Injuries: 1 Fatal.

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

On November 10, 2015, about 1858 central standard time, a Cessna 182Q, single engine airplane, N96381, impacted obstructions and terrain during an off-airport emergency landing near Richmond, Missouri. The pilot was fatally injured and the airplane was substantially damaged. The airplane was registered to 96381 Inc.; Ortonville, Michigan; and was operated by a private individual, as a 14 Code of Federal Regulations Part 91 personal flight. Dark night visual meteorological conditions (VMC) prevailed and a flight plan had not been filed. The airplane had departed Oakland County International Airport, (PTK) Pontiac, Michigan, about 1530 eastern standard time, and was destined for Charles B Wheeler Downtown Airport (MKC), Kansas City, Missouri.

The airplane was in cruise flight about 3,200 feet mean sea level (msl) and was receiving visual flight rules flight following from air traffic control at Kansas City. About ten minutes before the accident the pilot requested directions to the nearest airport and reported that airplane had a significant loss of engine power. The controller gave directions to Curtis Field Airport (8MO3), Richmond, Missouri, which was then about five miles southwest from the airplane. The last radar data showed that the descending airplane was about 1,600 feet msl and several minutes later radio contact was lost.

A witness about two miles northwest from 8MO3 saw the navigation lights and the landing light of the southbound airplane. He reported that the airplane passed directly overhead about 500 feet above him and the engine sounded like it was "spitting". The witness watched the lights of the airplane then proceed in the general direction of 8MO3. The airplane was more than a mile away, had completed a left turn and was proceeding almost due west when the witness saw the airplane descend and disappear from his sight. Shortly afterward he heard two distinct "thuds". The witness immediately contacted 9-1-1 emergency, an active search began, and the wreckage was found at 2126.

Evidence at the scene showed the airplane was northwest bound when it first struck an 80-foot tall tree, and was nearly nose down vertical when it impacted terrain. Adequate fuel was found in the airplane, but there was no postimpact fire.

The closest official weather reporting station was at KGPH, Mosby, Missouri; located 16 miles west from the accident location, At 1835 the Automated Surface Observation System at KGPH, reported wind from 120 degrees at 5 knots, visibility 10 miles, clear skies, temperature 17 degrees Celsius (C), dew point 8 degrees C, with an altimeter setting of 29.82 inches of Mercury.

Those who may have information that might be relevant to the National Transportation Safety Board investigation may contact them by email eyewitnessreport@ntsb.gov, and any friends and family who want to contact investigators about the accident should email assistance@ntsb.gov


Dr. Elizabeth McGhee


Dr. Elizabeth McGhee


Elizabeth McGhee with her son Merritt, 12, both of Oxford, helped fly gifts to foster care children on Dec. 3 from the Oakland County International Airport as part of Operation Good Cheer. More than 200 pilots volunteered to take the hundreds of gifts around the state.




Friends and family will gather this weekend to remember a selfless volunteer, accomplished veterinarian and mother of nine who died in a plane crash last week. 

Elizabeth McGhee, 57, of Ortonville, died Nov. 10 in a single-engine plane crash in Ray County, Missouri, according to the Kansas City Star. She was the only occupant of the plane.

McGhee, a Kansas native, was an accomplished veterinarian, pilot and 4-H leader, as well as a missionary to Africa, according to her obituary.

“She spent here life investing in the lives of other human beings all over the world,” said longtime friend Melanie Morris, officer manager of Lake Orion Veterinary Hospital, where McGhee worked. “She was my mentor and the mentor of many others in motherhood, homeschooling, as a 4-H leader, as a businessperson and she was very involved in her community as a 4-H leader, as a medical missionary, as a pilot, a beauty pageant contestant and as a Republican delegate.”

McGhee was also a former Oakland County Homemaker of the Year and, in 2011, used her Cessna 172 to deliver Christmas gifts to foster children around the state as part of Operation Good Cheer.

A memorial service for McGhee will be held at 11 a.m. on Saturday, Nov. 21, at the Auburn Hills Christian Center, located at 2592 East Walton Blvd. in Auburn Hills.

Church administrator Shelley Gilbert said McGhee was energetic and full of life and was involved in many activities, including mission work across the country and overseas.

“She had a passion for life and she was a very fun person to be around,” Gilbert said.

Cash or check memorials can be sent to Clarkston State Bank, attn: Elizabeth McGhee Legacy Fund; or Mercy in Truth Medical Missions, 721 North 31st, Kansas City, KS 66102.

In lieu of cut flowers, McGhee’s family asks friends and family to consider donating to either organization or perennials plant arrangements entrusted to Lewis E. Wint & Son Funeral Home, located at 5929 South Main St. in Clarkston.

An online guest book is available at www.wintfuneralhome.com.

- Source:  http://www.dailytribune.com



Dr. Elizabeth McGhee

Elizabeth McGhee (left), of Ortonville, with daughters Faith (middle) and Catherine (right) in this 2009 photo.


Dr. Elizabeth McGhee



In Memoriam of Dr. Elizabeth McGhee 
November 12, 1957 - November 10, 2015

DDr. Elizabeth C.(Stevens) McGhee; of Ortonville; Born in Wichita Kansas to Charles E. Stevens Jr. & E.C. Erin Stevens, Michigan died Suddenly on November 10, 2015; age 57; Survived by her children Grace E McGhee Seeley, Grant E. McGhee, Charles E. McGhee, Clark E. McGhee, Faith E.E. McGhee Miller, Catherine E. McGhee Pugh, Joseph E. McGhee, Madeline E. A. McGhee & Merritt M. McGhee; and her Mother- E.C. Erin Stevens; Sister of Catherine C. Gordon and Matthew M. Stevens; and five grandchildren, Binti, Charlette, Jack, Burliss, and Juniper.

Elizabeth, as an accomplished veterinarian, pilot, 4-H Leader, missionary to Africa and mother of many, her legacy is just beginning.

Celebration of life service is Saturday, November 21st at 11am, at Auburn Hills Christian Center in Auburn Hills, Michigan. 

Cash or check memorials my be sent to Clarkson State Bank Att: Elizabeth McGhee Legacy Fund, and/or Mercy in Truth Medical Missions, 721 N. 31st, Kansas City, KS 66102 for Africa Missions; In lieu of cut flowers, please consider donating to either organization or perennials plants arrangements entrusted to Lewis E. Wint & Son Funeral Home, Clarkston. Online guest book www.wintfuneralhome.com

Source:  http://www.wintfuneralhome.com

 
UPDATE (11/11/15) RICHMOND, Mo. — Missouri Highway Patrol identified the victim in Tuesday evening’s plane crash as a Michigan woman. 

12:15 p.m. — The pilot in Tuesday evening’s plane crash in Ray County has been identified.

Elizabeth Carleen-Stevens McGhee of Ortonville, Michigan pilot was traveling from KC to Michigan when her plane went down near Highway 13 and Route B sometime after 7:00 p.m. A search for the craft began after a distress signal was received by authorities.

She was pronounced dead by the Ray County Coroner. An investigation into the cause of the crash is ongoing. Her name is expected to be released Wednesday afternoon.

ORIGINAL (11/10/15)

10:54 p.m. — The pilot of a small aircraft that crashed in Ray County Tuesday night has died.

According to the Missouri State Highway Patrol, a distress call was received from the plane after 7:00 p.m. prompting an air and ground search for the plane. It was found around 9:30 p.m. near Richmond at Highway 13 and Route B.

The Ray County Sheriff’s Department says the pilot was the only person in the plane at the time of the crash. The pilot’s identity is not being released at this time.

Sources: 

http://fox4kc.com


http://www.kmbc.com

  
http://www.kshb.com


http://www.kctv5.com


http://www.kmzu.com


RAY COUNTY, Mo. - UPDATE 11/11| Missouri Highway Patrol identified the victim killed in a single-engine plane crash early Tuesday night.

The victim has been identified as 57-year-old Elizabeth Carleen-Stevens McGhee. According to reports, Thursday would’ve been her 58th birthday.

Officials are still investigating the cause of the crash. 

ORIGINAL STORY:

One person is dead following a single-engine plane crash in Ray County, Mo.

Ray County Sheriff’s Deputies and the Missouri Highway Patrol were called out after 7:30 p.m. to an area north of Richmond, Mo. on reports that a small plane had lost contact with air traffic controllers.

According to reports, emergency crews combed the rural area for the plane for nearly two hours before locating it near Missouri Highway 13 and Dockery Road. A 41 Action News photographer found the scene near 134th St.

Troopers say one person was killed in the crash.   Investigators remain on scene trying to learn more about the circumstances of the crash.