BE9L pilot reported landing on a runway marked closed; but no NOTAM.

Narrative:

We departed for ZZZ1. We checked the weather via our ipad gamin pilot app linked to garmin weather service. We observed a narrow line of weather moving through the ZZZ1 area. We hoped it would pass before we arrived. Enroute about 25 minutes from ZZZ1 we were informed by ATC that the weather still looked bad at ZZZ1 but that it was dissipating and moving out. They gave us the option to try and work our way around the worst of it and try to sneak in on the south side. We opted to divert since we do not have good onboard radar. We asked ATC about ZZZ2; but they informed us that the weather was just over ZZZ2. We then opted to try for ZZZ. We listened to the weather; and it was VFR. We checked notams via the garmin app; and all looked well. There were 4 notams. Com remote outlet out of service; navigation VOR/DME out of service; runway xx PAPI out of service; obst tower light out of service. ATC also read us the notams. We asked for and received clearance to shoot the RNAV 18 into ZZZ. Once established on the approach we had a visual on the runway and canceled IFR in the air with ATC. The rest of the approach continued with no issues. As I pulled into the flare on runway xx; I observed some debris on the numbers of xx. I floated the airplane beyond the debris and landed safely. I then taxied back to the numbers to see what was there. It was then I discovered an X on the runway. They looked like sizeable tarp-like material held down by sandbags. Had we landed on the numbers we indeed would have hit them and damaged the aircraft and perhaps been harmed as well. We then taxied to the other end of the runway and discovered an X there too. We rechecked notams to make sure we did not miss something. No NOTAM of runway closer was present. I called the briefer; and he also confirmed there was no NOTAM but was alarmed to find out there was xs on the runway. He called the airport manager; and a NOTAM was issued leaving us stuck at the airport. The only other runway is grass and not suitable for our king air to depart. We called the airport manager who apologized for the considerable oversight. The assistant manager was supposed to issue the NOTAM; but it was overlooked. The runway lights were on; beacon working; no NOTAM and the xs had no lights on them. The manager came out to the airport; removed the xs; removed the NOTAM; and we departed without incident.

Original NASA ASRS Text

Title: BE9L pilot reported landing on a runway marked closed; but no NOTAM.

Narrative: We departed for ZZZ1. We checked the weather via our iPad Gamin Pilot App linked to Garmin Weather Service. We observed a narrow line of weather moving through the ZZZ1 area. We hoped it would pass before we arrived. Enroute about 25 minutes from ZZZ1 we were informed by ATC that the weather still looked bad at ZZZ1 but that it was dissipating and moving out. They gave us the option to try and work our way around the worst of it and try to sneak in on the south side. We opted to divert since we do not have good onboard radar. We asked ATC about ZZZ2; but they informed us that the weather was just over ZZZ2. We then opted to try for ZZZ. We listened to the weather; and it was VFR. We checked NOTAMs via the Garmin App; and all looked well. There were 4 NOTAMs. Com remote outlet out of service; NAV VOR/DME out of service; RWY XX PAPI out of service; OBST Tower Light out of service. ATC also read us the NOTAMs. We asked for and received clearance to shoot the RNAV 18 into ZZZ. Once established on the approach we had a visual on the runway and canceled IFR in the air with ATC. The rest of the approach continued with no issues. As I pulled into the flare on Runway XX; I observed some debris on the numbers of XX. I floated the airplane beyond the debris and landed safely. I then taxied back to the numbers to see what was there. It was then I discovered an X on the runway. They looked like sizeable tarp-like material held down by sandbags. Had we landed on the numbers we indeed would have hit them and damaged the aircraft and perhaps been harmed as well. We then taxied to the other end of the runway and discovered an X there too. We rechecked NOTAMs to make sure we did not miss something. No NOTAM of runway closer was present. I called the briefer; and he also confirmed there was no NOTAM but was alarmed to find out there was Xs on the runway. He called the airport manager; and a NOTAM was issued leaving us stuck at the airport. The only other runway is grass and not suitable for our King Air to depart. We called the Airport Manager who apologized for the considerable oversight. The Assistant Manager was supposed to issue the NOTAM; but it was overlooked. The runway lights were on; beacon working; no NOTAM and the Xs had no lights on them. The manager came out to the airport; removed the Xs; removed the NOTAM; and we departed without incident.

Data retrieved from NASA's ASRS site 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.

Attributes
ACN	1574532
Time
Date	201808
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	King Air C90 E90
Operating Under FAR Part	Part 91
Flight Phase	Landing
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Pilot Flying
Qualification	Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 214 Flight Crew Total 4591 Flight Crew Type 245
Events
Anomaly	Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown Ground Incursion Runway Inflight Event / Encounter Weather / Turbulence