Narrative:

IOE flight; I was acting as pilot flying on a familiarization flight to cak. The flight was proceeding as normal. We were cleared for the visual into cak. While flying; I was focused on the runway to make sure I was not going to overshoot since I had never been there before. Instead of spinning in pattern altitude; I spun in an altitude that was below pattern. When we descended and I was looking at the runway; an aural alert went off when the gear was not down that I was slightly less than 1;000 ft above terrain within the airport environment. I quickly corrected to a correct altitude and was fully configured and stable for the approach at the correct altitudes and speeds.there was an aural alert that the gear was not down and we both confirmed it was an incorrect input of the altitude while cleared for the visual approach to landing.I was on IOE and differences training at an unfamiliar airport. The bug was spun too fast and I did not reconfirm it with the check airman was we were cleared for the approach into cak.when the error was identified; I quickly corrected my altitude back to a safe level prior to turning final to continue my visual approach to landing.poh calls for reconfirming altitude changes after any inputs are made with the flying check pilot. I have since studied in detail each airport flown into the night prior to make sure I am more familiar with the airport and appropriate altitudes. When expecting a visual approach I also confirm appropriate pattern altitude for that airport in my approach/arrival briefing to make sure I am making a mental note of it along with having the captain on the same page as me.

Google
 

Original NASA ASRS Text

Title: An aircrew on approach descended below 1;000 FT not configured for landing. An aural alert sounded; they returned to the correct altitude; configured the aircraft and landed.

Narrative: IOE FLT; I was acting as Pilot Flying on a familiarization FLT to CAK. The FLT was proceeding as normal. We were cleared for the visual into CAK. While flying; I was focused on the runway to make sure I was not going to overshoot since I had never been there before. Instead of spinning in pattern altitude; I spun in an altitude that was below pattern. When we descended and I was looking at the runway; an aural alert went off when the gear was not down that I was slightly less than 1;000 Ft above terrain within the airport environment. I quickly corrected to a correct altitude and was fully configured and stable for the approach at the correct altitudes and speeds.There was an aural alert that the gear was not down and we both confirmed it was an incorrect input of the altitude while cleared for the visual approach to landing.I was on IOE and differences training at an unfamiliar airport. The bug was spun too fast and I did not reconfirm it with the check airman was we were cleared for the approach into CAK.When the error was identified; I quickly corrected my altitude back to a safe level prior to turning final to continue my visual approach to landing.POH calls for reconfirming altitude changes after any inputs are made with the Flying Check Pilot. I have since studied in detail each airport flown into the night prior to make sure I am more familiar with the airport and appropriate altitudes. When expecting a visual approach I also confirm appropriate pattern altitude for that airport in my approach/arrival briefing to make sure I am making a mental note of it along with having the Captain on the same page as me.

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.