A falcon 2000 first officer reported a crossing restr undershoot due to the captain's setting the altimeter improperly near hpn.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	570617
Time
Date	200301
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : hpn.airport
State Reference	NY
Altitude	msl bound lower : 16000 msl bound upper : 17000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : n90.tracon tracon : acy.tracon
Operator	general aviation : corporate
Make Model Name	Falcon 2000
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : bouno
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 6000 flight time type : 300
ASRS Report	570617
Person 2
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : published procedure non adherence : far non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	controller : issued advisory
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flying the bonoo 3 arrival into hpn. Assigned to cross a fix at 17000 ft. While descending through FL180, I set my altimeter to 29.35 which was the local altimeter. I stated 'leaving 18000FT' and stated the altimeter was 29.35. I also had 29.35 set in the standby altimeter. I put that in when we were given the crossing restr and altimeter setting. I then went off on the other radio to obtain the ATIS report at hpn. I announced my intentions with the captain which he acknowledged as ok. During this time, the captain had incorrectly set his altimeter to 30.35. I did not realize this and it resulted in being 1000 ft below the crossing restr. When ATC advised us of the altitude deviation, I first thought it was an incorrect transponder readout. I then saw the captain's altimeter setting. I told him it was incorrect. He reset his transponder and the flight continued without incident. The captain was aware of the correct altimeter setting. I mentioned it 3 times to him, he just set it wrong. I don't think he was looking for the 29 portion of the altimeter setting. He was just looking at the 35 portion.

Original NASA ASRS Text

Title: A FALCON 2000 FO RPTED A XING RESTR UNDERSHOOT DUE TO THE CAPT'S SETTING THE ALTIMETER IMPROPERLY NEAR HPN.

Narrative: FLYING THE BONOO 3 ARR INTO HPN. ASSIGNED TO CROSS A FIX AT 17000 FT. WHILE DSNDING THROUGH FL180, I SET MY ALTIMETER TO 29.35 WHICH WAS THE LCL ALTIMETER. I STATED 'LEAVING 18000FT' AND STATED THE ALTIMETER WAS 29.35. I ALSO HAD 29.35 SET IN THE STANDBY ALTIMETER. I PUT THAT IN WHEN WE WERE GIVEN THE XING RESTR AND ALTIMETER SETTING. I THEN WENT OFF ON THE OTHER RADIO TO OBTAIN THE ATIS RPT AT HPN. I ANNOUNCED MY INTENTIONS WITH THE CAPT WHICH HE ACKNOWLEDGED AS OK. DURING THIS TIME, THE CAPT HAD INCORRECTLY SET HIS ALTIMETER TO 30.35. I DID NOT REALIZE THIS AND IT RESULTED IN BEING 1000 FT BELOW THE XING RESTR. WHEN ATC ADVISED US OF THE ALTDEV, I FIRST THOUGHT IT WAS AN INCORRECT XPONDER READOUT. I THEN SAW THE CAPT'S ALTIMETER SETTING. I TOLD HIM IT WAS INCORRECT. HE RESET HIS XPONDER AND THE FLT CONTINUED WITHOUT INCIDENT. THE CAPT WAS AWARE OF THE CORRECT ALTIMETER SETTING. I MENTIONED IT 3 TIMES TO HIM, HE JUST SET IT WRONG. I DON'T THINK HE WAS LOOKING FOR THE 29 PORTION OF THE ALTIMETER SETTING. HE WAS JUST LOOKING AT THE 35 PORTION.

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