Narrative:

First error: failure to learn 'all available information' about destination airport. Second: judgement call, landed on taxiway (parallel to runway 18/36) after arriving and finding runway closed (yellow X's). WX was good (by website) for VFR bfi-74S. Got abbreviated WX briefing from sea AFSS, did not request NOTAMS. Briefer knew my destination, said nothing. Also, had VFR flight following and none of 3 controllers (sea approach, ZSE, nuw approach) informed me of closure. Saw X's for closed runway after canceling advisories. Called unicom for airport advisory, no response, but an aircraft on ground indicated he was taxiing and had either landed or was about to depart from the taxiway. Therefore, I deduced taxiway was available and I landed without incident. Departed same way 10 mins later. Later I phoned FSS and learned the (only) runway (18/36) is notamed as closed, but the airport is open. I phoned the airport manager -- no answer -- I still don't know whether the airport has formally designated the taxiway as available and FSS has no information. However, the runway closure but airport open suggests taxiway is ok. Nevertheless, it was poor judgement on my part to land and depart without knowing for sure. (The entire taxiway was visibly clear and there are no 'hidden' or difficult-to-see entrances to it). Both failure to learn airport status and the landing judgement call were my responsibility. I'll sure ask for NOTAMS pertinent to my destination in the future. And next time I find an only runway closed, I will land elsewhere and call before landing. However, I think a small amount of responsibility lies with FSS and ATC -- it's surprising nobody said anything about the runway closure, even if I didn't ask. There were lots of opportunities!

Google
 

Original NASA ASRS Text

Title: C182 PLT FOUND THE RWY AT 74S CLOSED, SO HE LANDED ON THE PARALLEL TXWY. HE THEN TOOK OFF FROM THE TXWY.

Narrative: FIRST ERROR: FAILURE TO LEARN 'ALL AVAILABLE INFO' ABOUT DEST ARPT. SECOND: JUDGEMENT CALL, LANDED ON TXWY (PARALLEL TO RWY 18/36) AFTER ARRIVING AND FINDING RWY CLOSED (YELLOW X'S). WX WAS GOOD (BY WEBSITE) FOR VFR BFI-74S. GOT ABBREVIATED WX BRIEFING FROM SEA AFSS, DID NOT REQUEST NOTAMS. BRIEFER KNEW MY DEST, SAID NOTHING. ALSO, HAD VFR FLT FOLLOWING AND NONE OF 3 CTLRS (SEA APCH, ZSE, NUW APCH) INFORMED ME OF CLOSURE. SAW X'S FOR CLOSED RWY AFTER CANCELING ADVISORIES. CALLED UNICOM FOR ARPT ADVISORY, NO RESPONSE, BUT AN ACFT ON GND INDICATED HE WAS TAXIING AND HAD EITHER LANDED OR WAS ABOUT TO DEPART FROM THE TXWY. THEREFORE, I DEDUCED TXWY WAS AVAILABLE AND I LANDED WITHOUT INCIDENT. DEPARTED SAME WAY 10 MINS LATER. LATER I PHONED FSS AND LEARNED THE (ONLY) RWY (18/36) IS NOTAMED AS CLOSED, BUT THE ARPT IS OPEN. I PHONED THE ARPT MGR -- NO ANSWER -- I STILL DON'T KNOW WHETHER THE ARPT HAS FORMALLY DESIGNATED THE TXWY AS AVAILABLE AND FSS HAS NO INFO. HOWEVER, THE RWY CLOSURE BUT ARPT OPEN SUGGESTS TXWY IS OK. NEVERTHELESS, IT WAS POOR JUDGEMENT ON MY PART TO LAND AND DEPART WITHOUT KNOWING FOR SURE. (THE ENTIRE TXWY WAS VISIBLY CLR AND THERE ARE NO 'HIDDEN' OR DIFFICULT-TO-SEE ENTRANCES TO IT). BOTH FAILURE TO LEARN ARPT STATUS AND THE LNDG JUDGEMENT CALL WERE MY RESPONSIBILITY. I'LL SURE ASK FOR NOTAMS PERTINENT TO MY DEST IN THE FUTURE. AND NEXT TIME I FIND AN ONLY RWY CLOSED, I WILL LAND ELSEWHERE AND CALL BEFORE LNDG. HOWEVER, I THINK A SMALL AMOUNT OF RESPONSIBILITY LIES WITH FSS AND ATC -- IT'S SURPRISING NOBODY SAID ANYTHING ABOUT THE RWY CLOSURE, EVEN IF I DIDN'T ASK. THERE WERE LOTS OF OPPORTUNITIES!

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.