Four people were hospitalized after a small plane crashed and ended up on the front lawn of an Arvada home Friday morning, according to the Arvada Fire Protection District.

Two adults and two children were taken to hospitals after the small plane they were traveling in crashed in an Arvada neighborhood near Oberon Road and Brentwood Street, Arvada Fire spokesperson Deanna Harrington said.

Information about the severity of their injuries was not immediately available, but Harrington confirmed everyone involved in the crash was out of the plane when first responders arrived on scene.

There were no fatalities at the scene, Harrington added, and the four people hospitalized are believed to have been riding in the plane.

Preliminary information indicates the single-engine Beechcraft 35 took off from Centennial Airport at 9:16 a.m. and crashed around 9:30 a.m., according to the flight tracking website FlightAware and the National Transportation Safety Board.

The pilot was presumably en route to the Rocky Mountain Metropolitan Airport in Jefferson County, but never finished the journey, said NTSB spokesperson Sarah Sulick.

“During the flight, the pilot communicated with local air traffic control the plane was experiencing engine issues and he planned to land at Rocky Mountain Airport,” Sulick said in an emailed statement to the Denver Post. “For unknown reasons, the pilot did not land at the airport and instead attempted a forced landing onto a road.”

That road was Oberon Road, and the crash site is near where the road intersects with Brentwood Street. Oberon Road runs parallel to the railroad tracks.

“I heard screaming that I’ll never forget for the rest of my life,” said Arvada resident Kent Murray, who lives just across the train tracks from the crash site.

Murray heard the plane crash from inside his home and assumed it was a car crash. But when he got outside, he saw a small, white plane had landed on Oberon Street and slid into a red pickup truck.

Noah Taht, a flight instructor at the Rocky Mountain Airport, was in the air when he heard the pilot call out over the radio that his plane was losing oil pressure and he was having engine trouble. The pilot called out an emergency declaration and didn’t think he could make it to the airport.

“He said he was going to have to put it down somewhere and that’s the last I heard from him,” Taht said.

Taht visited the Arvada crash site after he landed to see what happened. He said the pilot did a good job of avoiding houses and powerlines.

“He put it down exactly where he was supposed to,” Taht said.

Other witnesses say the plane was coming in low, clipped a fence and skidded down Oberon Road before hitting the truck.

A photo posted by the Arvada Police Department shows wreckage from the plane strewn across the front lawn of a home on Oberon Road, next to a red pickup truck the plane collided with during the crash.

Arvada Fire Protection District crews responded to reports of an aircraft emergency around 9:40 a.m. Friday, Fire Operations Chief Matt Osier said. The plane was on fire when crews arrived on scene.

Although the fire department originally reported a potential structure fire associated with the crash, Osier said the flames were contained to the plane and did not spread to the surrounding homes. He said it was unclear if the fire started before or after the plane crashed.

The photo from the police department shows a propellor, possibly from the nose of the small plane, lodged in the truck’s front right tire. Soot and other debris is scattered across the sidewalk, the side of the truck and the lawn.

The NTSB and the FAA will investigate the crash.

“An NTSB investigator arrived on scene this afternoon to begin the process of documenting the scene and examining the aircraft,” Sulick said. “The aircraft will then be recovered to a secure facility for further evaluation.”

Investigators will look into flight tracking data, recordings of air traffic control communications, aircraft maintenance records, weather forecasts and actual weather, the pilot’s license and experience, witness statements and any available surveillance video, Sulick said.

Witnesses to the accident or those who have surveillance video or other information that could be relevant to the investigation are asked to contact the NTSB at witness@ntsb.gov.