John Barranco, who lost his daughter Terresa Teutenberg, son-in-law Fred and their five children in the July 9, 2011, crash, said an NTSB investigator sent him the complete report last week.

In addition to the six-page summary posted to the NTSB’s website, Barranco also had access to 44 files, including photos, transcripts of 911 calls and interviews with rescue workers.

“When I read it, it tore at my heart,” said Barranco, who lives in northern Georgia.

Fred, a certified private pilot, was flying his family home from a reunion in St. Louis when he reported trouble with the right engine, according to the report.

Weather conditions were clear and there were no reported maintenance problems with the plane. Fred had an estimated 1,000 hours of flying time, including seven single-engine practice landings in the plane that crashed.

The plane took off about 3:20 p.m. and had been flying for two hours when Fred declared an emergency because of a rough-running engine, the report said. Air traffic controllers in Atlanta directed him to an airport 10 miles away in Demopolis, Ala. He located the airport and circled it while descending to 17,000 feet, the report said.

Several moments after his initial report of engine trouble, he told controllers he had shut down the right engine. He also told them he did not believe he would require any assistance after landing and reported that the airport was in sight.

He was cleared for a visual approach and was last observed on the radar at an altitude of 700 feet, about three miles from the approach end of the runway, the report said.

Fred’s last communication with the tower was a request to change radio frequency to the local traffic advisory frequency, the report said. That was about nine minutes after he first called for help.

Six hours later, plane wreckage was spotted in a densely wooded area less than a mile from the end of the airport’s only runway.

Although the summary did not explain the delay, Barranco said additional documentation indicated that no one locally knew a plane might be missing until the Atlanta air traffic controllers called and asked if the plane had landed safely.

A local pilot went up and searched the area until it got dark, but didn’t see the wreckage.

“From the beginning, they didn’t know if they diverted to a different airport or what,” said Barranco, who added that wildlife officials finally smelled the burning wreckage and were able to help pinpoint its location.

Near daylight, the first rescuers reached the scene on all-terrain vehicles.

“The amount of people that got involved on the search of this thing was phenomenal,” Barranco said. “It was something that you’d see in the movies or read in a novel, but don’t expect to experience it.”

Rescue crews found the plane upside down amid trees that were about 80 feet tall. Their tops had been sheered off about 70 feet from the plane.

The plane’s landing gear was down and flaps were extended, indicating the pilot was preparing to land.

The cockpit and cabin were heavily damaged by fire, the report said.

Barranco, who read the coroner’s report, said the family died of blunt force impact.

“I think what happened is once they hit the trees, it broke off the right wing and it just flipped the rest of the plane and wound up upside down on the ground,” he said.

“The plane was at least two-thirds full of gas,” he added. “My son-in-law always tops off the tanks just in case he has to divert because of weather. He was very conscientious of safety.”

The next document NTSB will release in its crash investigation is the probable cause report. That report, unlike the factual report released last week, will draw conclusions about what likely caused the crash.

Barranco said he hopes it will be released before the end of the year.

“It took over 16 months to get (this report) done, but then again this is the NTSB and they have a lot to do,” he said. “I’m not faulting them too much on the time it takes, but like anything, you want answers as soon as you can.”

John Barranco, who lost his daughter Terresa Teutenberg, son-in-law Fred and their five children in the July 9, 2011, crash, said an NTSB investigator sent him the complete report last week.

In addition to the six-page summary posted to the NTSB’s website, Barranco also had access to 44 files, including photos, transcripts of 911 calls and interviews with rescue workers.

“When I read it, it tore at my heart,” said Barranco, who lives in northern Georgia.

Fred, a certified private pilot, was flying his family home from a reunion in St. Louis when he reported trouble with the right engine, according to the report.

Weather conditions were clear and there were no reported maintenance problems with the plane. Fred had an estimated 1,000 hours of flying time, including seven single-engine practice landings in the plane that crashed.

The plane took off about 3:20 p.m. and had been flying for two hours when Fred declared an emergency because of a rough-running engine, the report said. Air traffic controllers in Atlanta directed him to an airport 10 miles away in Demopolis, Ala. He located the airport and circled it while descending to 17,000 feet, the report said.

Several moments after his initial report of engine trouble, he told controllers he had shut down the right engine. He also told them he did not believe he would require any assistance after landing and reported that the airport was in sight.

He was cleared for a visual approach and was last observed on the radar at an altitude of 700 feet, about three miles from the approach end of the runway, the report said.

Fred’s last communication with the tower was a request to change radio frequency to the local traffic advisory frequency, the report said. That was about nine minutes after he first called for help.

Six hours later, plane wreckage was spotted in a densely wooded area less than a mile from the end of the airport’s only runway.

Although the summary did not explain the delay, Barranco said additional documentation indicated that no one locally knew a plane might be missing until the Atlanta air traffic controllers called and asked if the plane had landed safely.

A local pilot went up and searched the area until it got dark, but didn’t see the wreckage.

“From the beginning, they didn’t know if they diverted to a different airport or what,” said Barranco, who added that wildlife officials finally smelled the burning wreckage and were able to help pinpoint its location.

Near daylight, the first rescuers reached the scene on all-terrain vehicles.

“The amount of people that got involved on the search of this thing was phenomenal,” Barranco said. “It was something that you’d see in the movies or read in a novel, but don’t expect to experience it.”

Rescue crews found the plane upside down amid trees that were about 80 feet tall. Their tops had been sheered off about 70 feet from the plane.

The plane’s landing gear was down and flaps were extended, indicating the pilot was preparing to land.

The cockpit and cabin were heavily damaged by fire, the report said.

Barranco, who read the coroner’s report, said the family died of blunt force impact.

“I think what happened is once they hit the trees, it broke off the right wing and it just flipped the rest of the plane and wound up upside down on the ground,” he said.

“The plane was at least two-thirds full of gas,” he added. “My son-in-law always tops off the tanks just in case he has to divert because of weather. He was very conscientious of safety.”

The next document NTSB will release in its crash investigation is the probable cause report. That report, unlike the factual report released last week, will draw conclusions about what likely caused the crash.

Barranco said he hopes it will be released before the end of the year.

“It took over 16 months to get (this report) done, but then again this is the NTSB and they have a lot to do,” he said. “I’m not faulting them too much on the time it takes, but like anything, you want answers as soon as you can.”