A corporate aircraft on the teb VOR 24 was issued an ATC low altitude alert at 500 ft but the crew f...

Narrative:

Flight was part 91 and I was flying in the right seat as the pilot not flying.we were being vectored for the ILS to runway 19 at teb but due to snow removal at the teb airport ATC i.e.; new york approach changed the approach to the VOR 24 to teb. ATC changed it when we were about 10 NM from the airport necessitating some quick thinking and re-briefing of the new approach all the while being fairly close to the airport on vectors.as a crew I feel that we did a good job of briefing the new approach i.e.; VOR 24. The pilot flying seemed to be a little confused as to whether he could fly this approach using blue needles (GPS) vs. Green needles (raw approach VOR) and I conveyed to him that we could indeed fly the approach in blue needles (GPS). Instead he previewed the approach in blue needles but then switched to green needles without really advising me what he was doing. This pilot has a history of poor crew resource management (CRM) and it was evident during this approach. Should we have abandoned the approach? No I don't think so because I simply reverted to monitoring the approach as he flew as raw data VOR approach and not GPS.because the pilot flying used raw data green needles approach he was unable to use the VNAV function of the flight guidance control (FGC) and instead this approach became a so called dive and drive using vertical speed on the FGC down to the MDA of 500 ft MSL.the approach seemed to be doing well when teb tower called us and said that they had a low altitude alert on us. I had been monitoring the altitudes on the approach and looked again and saw we were at the MDA of 500 ft MSL which is in the parameters of the approach. I'm not sure why teb tower saw a low altitude alert on our aircraft.we saw the runway at about 2.5 NM and made a stabilized approach and landed on runway 24.this particular pilot who was the pilot flying did not want to de-brief and I think in retrospect he should have been clearer as to how he was going to fly this approach utilizing the FGC. Poor CRM on his part and I should of been more assertive with asking questions during the briefing.

Original NASA ASRS Text

Title: A Corporate aircraft on the TEB VOR 24 was issued an ATC low altitude alert at 500 FT but the crew felt that altitude was within the MDA parameters. Poor CRM was noted during the approach preparation phase.

Narrative: Flight was Part 91 and I was flying in the right seat as the pilot not flying.We were being vectored for the ILS to Runway 19 at TEB but due to snow removal at the TEB airport ATC i.e.; New York Approach changed the approach to the VOR 24 to TEB. ATC changed it when we were about 10 NM from the airport necessitating some quick thinking and re-briefing of the new approach all the while being fairly close to the airport on vectors.As a crew I feel that we did a good job of briefing the new approach i.e.; VOR 24. The pilot flying seemed to be a little confused as to whether he could fly this approach using blue needles (GPS) vs. Green needles (raw approach VOR) and I conveyed to him that we could indeed fly the approach in blue needles (GPS). Instead he previewed the approach in blue needles but then switched to green needles without really advising me what he was doing. This pilot has a history of poor crew resource management (CRM) and it was evident during this approach. Should we have abandoned the approach? No I don't think so because I simply reverted to monitoring the approach as he flew as raw data VOR approach and not GPS.Because the pilot flying used raw data green needles approach he was unable to use the VNAV function of the Flight Guidance Control (FGC) and instead this approach became a so called dive and drive using vertical speed on the FGC down to the MDA of 500 FT MSL.The approach seemed to be doing well when TEB Tower called us and said that they had a low altitude alert on us. I had been monitoring the altitudes on the approach and looked again and saw we were at the MDA of 500 FT MSL which is in the parameters of the approach. I'm not sure why TEB Tower saw a low altitude alert on our aircraft.We saw the runway at about 2.5 NM and made a stabilized approach and landed on Runway 24.This particular pilot who was the pilot flying did not want to de-brief and I think in retrospect he should have been clearer as to how he was going to fly this approach utilizing the FGC. Poor CRM on his part and I should of been more assertive with asking questions during the briefing.

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

Attributes
ACN	1063556
Time
Date	201301
Local Time Of Day	1801-2400
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	Marginal
Light	Night
Aircraft 1
Make Model Name	Gulfstream V / G500 / G550
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 40 Flight Crew Total 10600 Flight Crew Type 2000
Events
Anomaly	Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT

A corporate aircraft on the teb VOR 24 was issued an ATC low altitude alert at 500 ft but the crew felt that altitude was within the MDA parameters. Poor CRM was noted during the approach preparation phase.