Date: 202011
Local time of day: 1801-2400
Location: BED.Airport, MA
Flight conditions: VMC
Weather elements / visibility: 25
Light: Night
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D BED
ATC / advisory: Tower BED
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Distraction; Fatigue; Training / Qualification
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors; Airport
Primary problem: Human Factors

Narrative: I was returning to BED from the West. It was dark. I tuned in the ATIS. The current ATIS was broadcasting that BED was 'landing and departing Runway 23.' After copying the ATIS; I called BED Tower and reported my position as near Minuteman Airport (6B6) and informed the Tower that I was inbound landing with ATIS. The Tower Controller initially cleared me to enter a right downwind for Runway 29.  This confused me because the ATIS had stated that BED was 'landing and departing Runway 23.' I asked the Controller for confirmation of the runway assignment and he acknowledged that he had 'made a mistake' and told me to enter a right downwind for Runway 23. After I entered the control space; and near the airport; I noticed the high intensity runway lights and landing traffic was on Runway 29; while runway 23 had their lights on 'dim'.  Since the ATIS had not mentioned simultaneous operations to intersecting runways; I became disoriented. I mistook Runway 29 for Runway 23. I was so concerned that I even called the Tower and asked the Controller: 'Is the Aircraft Y lined up with the right runway?'The Tower Controller realized that something was not right and called me and asked me to confirm that I was setting up for right downwind 23 and offered me a clearance to enter a right downwind for Runway 29. I told him that I thought I could still correct; but I ended up flying through the final for Runway 23 and ended up on a left downwind for 23. At about this time; another aircraft; which I later learned was Aircraft Z arriving from the west had also turned inbound to Runway 23 from the north. The Tower Controller told me to turn 20 degrees further right which I did to widen out my downwind leg. Thanks to the Controller; the Aircraft Z was able to land safely and so was I.I now realize that several other factors contributed to my confusion.  I was more tired than I realized. I had a very long work week; yet this night was an opportunity to start flying more night flights; after being absent from this experience for over 16 months.  The pandemic means hazard [but not] if I bring an instructor to help me re-acquaint to night flying.   I allowed myself to be fooled by the warm weather; the light winds and the great visibility into thinking that it would be a good night to re-acquaint myself to cross-country night flying.  Tonight; with the lights dimmed in the cockpit; and the high intensity lights on Runway 29; a plane landing on 29; the lights dimmed on Runway 23; and my lack of night flying practice did this happen.I now realize that I had vastly underestimated the combined effects of fatigue; distraction and 'rust.' Added to that; my confusion resulting from the initial mistaken clearance to enter a right downwind for 29; the combination of bright runway lighting on a conflicting runway without any warning that such operations were being conducted; and traffic operating in unexpected directions all combined to make for a much more confusing situation than I ever would have expected.The controllers explained to me that even when Runway 23 is the operating runway; they still allow traffic to land and depart Runway 29 because Runway 23 is too short for some aircraft that use the field. Nevertheless; I believe that safety would be greatly improved if; during nighttime operations; the ATIS included the warning concerning operations being conducted simultaneously to conflicting runways. This is especially true at BED where runway alignment issues are already an issue. I believe that such a warning would have eliminated my confusion at seeing traffic landing and departing on Runway 29 and then mistaking it for Runway 23.




Synopsis: GA Pilot reported an airborne conflict after confusion identifying the correct runway for a night visual landing at BED airport.  Reporter cited lack of flying due to the COVID-19 pandemic was a contributing factor.