Just in case someone might be able to help. The site is www.n2700q.com
Thanks. I’ve corrected my posting.
Thanks for posting that. I’m the missing girl’s uncle. I fly out of PAE, up here in Washington State. It’s awfully rugged country down there so maybe not surprising that CAP hasn’t found anything. One more weekend and I think they’ll call it quits … but we never will.
We’re mapping all places searched – even places visited by “geocachers” since 9/24 – so as not to waste time turning over the same rocks. N2700Q is still out there somewhere … probably in a gorge where the sun doesn’t hit this time of year, or in the trees.
If you go into the AZ outback – esp. on the ground – log your coords and send me the data. Everyhting helps. Thanks.
This was in yesterdays FAA accident report. No one is saying anything so I assume no one saw it.
** Report created 4/28/2009 Record 2 **
IDENTIFICATION
Regis#: 2700Q Make/Model: C182 Description: 182, Skylane
Date: 09/24/2006 Time: 0000
Event Type: Accident Highest Injury: Fatal Mid Air: N Missing: N
Damage: Destroyed
LOCATION
City: SEDONA State: AZ Country: US
DESCRIPTION
AIRCRAFT CRASHED UNDER UNKNOWN CIRCUMSTANCES, WAS THE SUBJECT OF AN ALERT
NOTICE ISSUED 9/24/2006, THE TWO PERSONS ON BOARD WERE FATALLY INJURED,
SEARCH SUSPENDED 10/16/2006, WRECKAGE LOCATED 4/20/09 5 MILES FROM SEDONA,
AZ
INJURY DATA Total Fatal: 2
# Crew: 1 Fat: 1 Ser: 0 Min: 0 Unk:
# Pass: 1 Fat: 1 Ser: 0 Min: 0 Unk:
# Grnd: Fat: 0 Ser: 0 Min: 0 Unk:
WEATHER: NOT REPORTED
OTHER DATA
Activity: Unknown Phase: Unknown Operation: OTHER
FAA FSDO: SCOTTSDALE, AZ (WP07) Entry date: 04/27/2009
This was in yesterdays FAA accident report. No one is saying anything so I assume no one saw it.
** Report created 4/28/2009 Record 2 **
IDENTIFICATION
Regis#: 2700Q Make/Model: C182 Description: 182, Skylane
Date: 09/24/2006 Time: 0000Event Type: Accident Highest Injury: Fatal Mid Air: N Missing: N
Damage: DestroyedLOCATION
City: SEDONA State: AZ Country: USDESCRIPTION
AIRCRAFT CRASHED UNDER UNKNOWN CIRCUMSTANCES, WAS THE SUBJECT OF AN ALERT
NOTICE ISSUED 9/24/2006, THE TWO PERSONS ON BOARD WERE FATALLY INJURED,
SEARCH SUSPENDED 10/16/2006, WRECKAGE LOCATED 4/20/09 5 MILES FROM SEDONA,
AZINJURY DATA Total Fatal: 2
# Crew: 1 Fat: 1 Ser: 0 Min: 0 Unk:
# Pass: 1 Fat: 1 Ser: 0 Min: 0 Unk:
# Grnd: Fat: 0 Ser: 0 Min: 0 Unk:WEATHER: NOT REPORTED
OTHER DATA
Activity: Unknown Phase: Unknown Operation: OTHERFAA FSDO: SCOTTSDALE, AZ (WP07) Entry date: 04/27/2009
We overlook how tiny and insignificant we are down in an area like that.
Hopefully the families will take some comfort from at least knowing what hapened.
The report didn’t indicate which direction from Sedona the accident occurred. A look at the topo map of Wilson Mountain at Topoquest shows very rugged territory all around Sedona.
He went north, up Loy Canyon until you can’t go any farther, then turned right (east) into the little box canyon. He got almost to the saddle and then crashed his Cessna into trees along the north wall. There isn’t much left to see. Warning: Do not fly there except in FlightSim – you won’t get out – classic box canyon scenario.
Don’t hold your breath for any sort of accurate NTSB report. They got the preliminary report wrong in almost every way you can imagine, including time of departure, fuel loading, last annual, and–most significantly–Last Known Position (NTSB: 9M NE of Sedona / Actual, per radar & CAP: 9M SW of Sedona).
FYI, the passenger was my niece. My brother and I spent years trying to get the NTSB to correct their report and got nothing but ATTITUDE. We flew and hiked countless miles and took hundreds of photos. MAST (Missing Aircraft Search Team) discovered the key piece of evidence (a small fire reported and photographed the same day of the crash), and I used our Google-Earth based search app and aerial photos to pinpoint. Thank god, Marcy is coming home at last.
Many questions remain about how the “official” search was handled, and why all the fire departments in the search area were not queried.
For the full story including news-links go to www.N2700Q.com.
zihuat,
The FAA found a VFR code on the radar tape they thought was N2700Q. Did this turn out to be the correct aircraft?
Any chance they survived the crash?
The N2700Q web site talked about other crash sites that were found. Were these sites known or unknown?
Frank Holbert
160knots.com
We have the entire radar track, up until they reached the LKP.
The last section of it is shown in this pic: digitalbucket.net/view/9e387 … ck-end.jpg
(Ignore the blips in the red box – those were from another aircraft, moving too fast for N2700Q)
We found many old wrecks, some of which were mismarked by CAP/NTSB. Our efforts to provide them with new coords were not welcomed.
The closed-mind approach of OUR public agencies is something we’re hoping to make more people aware of, and to incite changes. If AZDEMA had done their job properly, and queried fire departments, this aircraft could have been found within hours.
We have the entire radar track, up until they reached the LKP.
The last section of it is shown in this pic: digitalbucket.net/view/9e387 … ck-end.jpg(Ignore the blips in the red box – those were from another aircraft, moving too fast for N2700Q)
We found many old wrecks, some of which were mismarked by CAP/NTSB. Our efforts to provide them with new coords were not welcomed.
The closed-mind approach of OUR public agencies is something we’re hoping to make more people aware of, and to incite changes. If AZDEMA had done their job properly, and queried fire departments, this aircraft could have been found within hours.
Shame it took so long to locate, but I hope you and your family can have closure, my condolences.
WOW that is pretty crazy and sad at the same time.