Yesterday a coworker and I decided to fly out to Lancaster PA to their
pilot shop because he wanted to look at purchasing a transceiver. This
was our first time flying together, but we did do the ATOP course at
Continental as a team. We decided that we would rent a plane from my
FBO and that we would fly out IFR with me under the hood and him as
safety. This way he not only makes it out to the pilot shop, but he
could log the time as PIC that I'm under the hood, and also see how an
instrument flight is conducted.

Those of you who live in the Northeast know that the winds have been
gusting upwards of 30 kts the past few days, but yesterday morning
brought calm winds and great viz, with forecasts showing that the
strong winds would return by 11am. The trip out was smoother than we
expected. Before reaching Reading PA, we picked up the Lancaster ATIS,
which stated that the visual approach was in use at Lancaster. I asked
the Reading controller whether he could coordinate an instrument
approach with the Harrisburg controller, which he did.

Once we were handed off to the Harrisburg controller we were told to
expect the VOR/DME 26 approach. As we continued inbound to Lancaster I
realized that we were still at 4000' about 10 miles out. Then we were
switched over to the tower, at which point he made it clear that I was
cleared for the visual approach. When I told him that I was expecting
the VOR/DME approach he sent me back to the approach controller. When
I asked the approach controller he told me that I was almost on top of
the final approach course between the Initial and Final Approach Fixes
and that I was cleared for the approach. Problem was that I was never
cleared for the approach, I was only told to expect the approach. I
take full responsibility for not querying the controller earlier and
not staying ahead of the plane.

I was able to intercept the final approach course about a mile outside
the FAF, but still about 1000' about the minimum altitude. I was able
to get down, but in hindsight I should have followed my mind and
either flown the missed or asked for vectors back to the approach.
While we were about two miles out a plane on the runway departed and
we were cautioned to watch for wake turbulence, in addition to holding
short of Rwy 31. I was right on the VASI but because I was concerned
about the wake turbulence I pulled the power before making it over the
threshold, didn't flare enough, and bounced it in. I added power and
was able to smooth it out, but it certainly wasn't the kind of landing
you want when you're flying with anyone, especially with another pilot
who you see fairly often. The approach was stabilized and the power
settings I had were working, so I should have known better than to
pull the power that soon.

On the way back to CDW the winds had picked up considerably and it was
a turbulent ride most of the way back. However, the 30kt headwind on
the way out was now a 30kt tailwind, giving us a groundspeed of about
140kts on the way back. I prepared for and received the LOC 22 back at
CDW and despite the turbulence down below 2000', managed to keep the
localizer centered throughout the approach. Even received a compliment
from the other pilot, but that wasn't enough to make me feel better
about the trip out to Lancaster.

It had been a month since I had last flown instruments, but usually
even after that long of a layoff I can come back with only minimal
rust. This time I had gotten behind the plane and hadn't kept my
situational awareness high enough. My last trip to the same airport
was with another pilot and had terminated in a well-coordinated full
VOR approach with a course reversal, and a good landing. I guess I had
gotten too accustomed to controllers making the approaches seamless,
but then again this was a perfect VFR day with almost no one flying
approaches. This will certainly make me more aware of where I'm at and
will lead me to question the controller if something doesn't seem
right.

Dave