Narrative:

I was flying an instrument proficiency flight. The flight was to fly practice approaches under IFR at con (concord; nh); mht (manchester; nh) and terminate with a practice approach and some VFR takeoffs and landings at ash. The [flight] was flown under IFR because marginal VFR conditions existed over the route; with ceilings ranging from 2;200 feet to 3;500 feet AGL; depending on location. Good visibility existed beneath the cloud deck. A safety pilot was on board and a view limiting device was used; because conditions were not solid IMC. Departing out of ash; I contacted boston approach and was cleared to climb to my assigned altitude of 4;000 feet MSL. After some vectoring for traffic; I was cleared to proceed direct to kersy; which is an IAF for the RNAV runway 17 approach at con. Since the aircraft was equipped with the G1000 system; much of the leg to kersy was flown on autopilot; while I tended to other tasks such as obtaining ASOS at con; briefing the approach; etc. Approximately 5 miles from kersy; I took over manual control and received the following clearance from boston approach: 'cross kersy at 4;000; cleared RNAV runway 17 approach at concord.' looking at my chart; the minimum altitude for the published segment from kersy to inkow (the next fix) was 4;400 feet MSL. It struck me odd that the controller would issue a crossing restriction that was lower than the minimum altitude for the segment I was about to enter. I was also aware that there was hilly terrain in that area and that there was likely good reason for the published altitude for that segment. I decided that after crossing kersy at 4;000 feet; I would then climb to 4;400 feet MSL; because I was cleared for the approach; and should be cleared to fly the procedure as published after making the requested crossing restriction.I climbed to 4;400 feet MSL and about 4 miles into the segment; the controller called me and advised: 'I see you have climbed to the published altitude of 4;400 feet. Just for future reference; when I assign a crossing altitude; I'm expecting you to fly that altitude for the segment.' he didn't sound upset; nor did he ask me to contact him on the ground after the flight. Based on the controller's tone; it did not appear as if any conflict was created by my action. He just made it clear that I did something he was not expecting. Needless to say; I immediately descended to 4;000 feet and proceeded with the approach to con. The rest of the flight was uneventful; and nothing further was said about the altitude situation at kersy.needless to say; I was a bit rattled by the incident. I pride myself on flying precisely and interacting as professionally as possible with ATC. I realize that it is not just my reputation that is on the line; but also that of the organization. In my previous experience; the only time I had ever been given an altitude assignment that was below published safe altitudes was while being vectored...never on a published approach segment. In addition; it has always been my understanding that once cleared for the approach; I was cleared to fly the procedure as published. Whenever a controller needed me higher than published on an approach segment; the controller would typically say: 'intercept and fly the route; maintain X thousand; expect approach clearance in X miles'; meaning once cleared; I could then fly the procedure at the published altitudes. Clearly; I need to get back with the aim and reread the material on approaches. At any rate; the deviation wasn't done maliciously; it was done for safety and because I believed at the time that it was the correct thing to do.

Google
 

Original NASA ASRS Text

Title: While on a practice instrument approach; there was a disagreement between the pilot and the Controller about the assigned altitude being below the published approach segment altitude.

Narrative: I was flying an instrument proficiency flight. The flight was to fly practice approaches under IFR at CON (Concord; NH); MHT (Manchester; NH) and terminate with a practice approach and some VFR takeoffs and landings at ASH. The [flight] was flown under IFR because marginal VFR conditions existed over the route; with ceilings ranging from 2;200 feet to 3;500 feet AGL; depending on location. Good visibility existed beneath the cloud deck. A safety pilot was on board and a view limiting device was used; because conditions were not solid IMC. Departing out of ASH; I contacted Boston Approach and was cleared to climb to my assigned altitude of 4;000 feet MSL. After some vectoring for traffic; I was cleared to proceed direct to KERSY; which is an IAF for the RNAV Runway 17 Approach at CON. Since the aircraft was equipped with the G1000 System; much of the leg to KERSY was flown on autopilot; while I tended to other tasks such as obtaining ASOS at CON; briefing the approach; etc. Approximately 5 miles from KERSY; I took over manual control and received the following clearance from Boston Approach: 'Cross KERSY at 4;000; cleared RNAV Runway 17 Approach at Concord.' Looking at my chart; the minimum altitude for the published segment from KERSY to INKOW (the next fix) was 4;400 feet MSL. It struck me odd that the controller would issue a crossing restriction that was LOWER than the minimum altitude for the segment I was about to enter. I was also aware that there was hilly terrain in that area and that there was likely good reason for the published altitude for that segment. I decided that AFTER crossing KERSY at 4;000 feet; I would then climb to 4;400 feet MSL; because I was cleared for the approach; and should be cleared to fly the procedure as published after making the requested crossing restriction.I climbed to 4;400 feet MSL and about 4 miles into the segment; the controller called me and advised: 'I see you have climbed to the published altitude of 4;400 feet. Just for future reference; when I assign a crossing altitude; I'm expecting you to fly that altitude for the segment.' He didn't sound upset; nor did he ask me to contact him on the ground after the flight. Based on the controller's tone; it did not appear as if any conflict was created by my action. He just made it clear that I did something he was not expecting. Needless to say; I immediately descended to 4;000 feet and proceeded with the approach to CON. The rest of the flight was uneventful; and nothing further was said about the altitude situation at KERSY.Needless to say; I was a bit rattled by the incident. I pride myself on flying precisely and interacting as professionally as possible with ATC. I realize that it is not just my reputation that is on the line; but also that of the organization. In my previous experience; the only time I had ever been given an altitude assignment that was BELOW published safe altitudes was while being vectored...never on a published approach segment. In addition; it has always been my understanding that once cleared for the approach; I was cleared to fly the procedure as published. Whenever a controller needed me higher than published on an approach segment; the controller would typically say: 'Intercept and fly the route; maintain X thousand; expect approach clearance in X miles'; meaning once cleared; I could then fly the procedure at the published altitudes. Clearly; I need to get back with the AIM and reread the material on approaches. At any rate; the deviation wasn't done maliciously; it was done for safety and because I believed at the time that it was the correct thing to do.

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.