Narrative:

We did flight planning using wsi computer at guard facility. Filed IFR flight plan with FOD FSS. Got NOTAMS from wsi computer sheet, WX briefer who accepted IFR flight plan at FOD FSS made no mention of a local NOTAM that had just been issued closing runway 15-33 at the dvn airport because of an accident investigation. Filed IFR to lit, layover 2 hours. Updated WX in lit asked for NOTAMS -- none. Depart lit for dvn on an IFR flight plan. Received visual approach into the dvn airport from quad city approach. No mention about runway closure. Dvn is about 8 mi northwest of quad city (moline). Quad city approach has jurisdiction over airspace. Cancelled IFR bout 6 mi out of dvn. Called unicom 3 times for advisories -- no response. Wind was 15/10 KTS. Flew over field, nothing unusual. Aircraft had crashed the day before and came to rest 1/2 to 3/4 of a mi off the departure end of 33. Aircraft was still there with vehicles around it. Nothing was observed on the runway or airport property. Entered downwind for 15. Called unicom to report downwind, base, final -- no response. No X's on runway -- no markings whatsoever to indicated closed runway. Landed without incident, but at the intersection of 3-21 and 15-33 were 2 small 4 ft high street barricades. We stopped without hitting them. They were totally invisible until you were within 300 ft of them. People on airport became irate that we landed on closed runway. (It was not marked as closed). Solution -- 1) local NOTAMS to include runway/airport closures are not distributed beyond local FSS. Anytime a runway is closed that is associated with an instrument approach for that runway which would affect landing mins should be an fdc NOTAM and properly distributed. 2) controller in quad city approach was aware of local NOTAM -- should have advised as it was a unique closure. 3) airport authorities should properly mark a runway closed, with proper X's. There was absolutely no indication at all!

Google
 

Original NASA ASRS Text

Title: MIL SMT LANDS ON CLOSED RWY AT DVN.

Narrative: WE DID FLT PLANNING USING WSI COMPUTER AT GUARD FACILITY. FILED IFR FLT PLAN WITH FOD FSS. GOT NOTAMS FROM WSI COMPUTER SHEET, WX BRIEFER WHO ACCEPTED IFR FLT PLAN AT FOD FSS MADE NO MENTION OF A LCL NOTAM THAT HAD JUST BEEN ISSUED CLOSING RWY 15-33 AT THE DVN ARPT BECAUSE OF AN ACCIDENT INVESTIGATION. FILED IFR TO LIT, LAYOVER 2 HRS. UPDATED WX IN LIT ASKED FOR NOTAMS -- NONE. DEPART LIT FOR DVN ON AN IFR FLT PLAN. RECEIVED VISUAL APCH INTO THE DVN ARPT FROM QUAD CITY APCH. NO MENTION ABOUT RWY CLOSURE. DVN IS ABOUT 8 MI NW OF QUAD CITY (MOLINE). QUAD CITY APCH HAS JURISDICTION OVER AIRSPACE. CANCELLED IFR BOUT 6 MI OUT OF DVN. CALLED UNICOM 3 TIMES FOR ADVISORIES -- NO RESPONSE. WIND WAS 15/10 KTS. FLEW OVER FIELD, NOTHING UNUSUAL. ACFT HAD CRASHED THE DAY BEFORE AND CAME TO REST 1/2 TO 3/4 OF A MI OFF THE DEP END OF 33. ACFT WAS STILL THERE WITH VEHICLES AROUND IT. NOTHING WAS OBSERVED ON THE RWY OR ARPT PROPERTY. ENTERED DOWNWIND FOR 15. CALLED UNICOM TO RPT DOWNWIND, BASE, FINAL -- NO RESPONSE. NO X'S ON RWY -- NO MARKINGS WHATSOEVER TO INDICATED CLOSED RWY. LANDED WITHOUT INCIDENT, BUT AT THE INTXN OF 3-21 AND 15-33 WERE 2 SMALL 4 FT HIGH STREET BARRICADES. WE STOPPED WITHOUT HITTING THEM. THEY WERE TOTALLY INVISIBLE UNTIL YOU WERE WITHIN 300 FT OF THEM. PEOPLE ON ARPT BECAME IRATE THAT WE LANDED ON CLOSED RWY. (IT WAS NOT MARKED AS CLOSED). SOLUTION -- 1) LCL NOTAMS TO INCLUDE RWY/ARPT CLOSURES ARE NOT DISTRIBUTED BEYOND LCL FSS. ANYTIME A RWY IS CLOSED THAT IS ASSOCIATED WITH AN INST APCH FOR THAT RWY WHICH WOULD AFFECT LNDG MINS SHOULD BE AN FDC NOTAM AND PROPERLY DISTRIBUTED. 2) CTLR IN QUAD CITY APCH WAS AWARE OF LCL NOTAM -- SHOULD HAVE ADVISED AS IT WAS A UNIQUE CLOSURE. 3) ARPT AUTHORITIES SHOULD PROPERLY MARK A RWY CLOSED, WITH PROPER X'S. THERE WAS ABSOLUTELY NO INDICATION AT ALL!

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.