Mr_Creepy said:
			
		
	
	
		
		
			Don we also had the 1000' stabilized rule at Mesa, Eagle and Midway.
I don't think you're unstabilized if you drop the nose a hair after MM and go about 1 dot low, just to give yourself more room to land, especially with any kind of headwind.
This discussion has gotten very technical but the main point is, any pilot with judgement is going to use all the runway available!
		
		
	 
Mr. Creepy,
I agree with you.  I think there is very sound logic for a pilot to readjust the flight path at the MM to land earlier in the touchdown zone than the ILS glideslope will allow.  
The ILS glideslope is only valid below the MM on ILS approaches that do not have a decision height.  Below the DH on ILS approaches it becomes a visual maneuver...and while I would always reference and maintain the glideslope to touchdown on a normal landing, the point should be emphasized that the glideslope is a reference and the pilot's visual picture is primary for landing below the DH/MM.
There was an accident back in the '70's....DC10....can't remember the airline...but they went low on the glideslope and hit approach lights.  However, there was no standard for G/S antenna location (as there is now...750' from the threshold)...and there was no published or standard TCH.  Now...all of that stuff is standard...the glideslope will always provide a a minimum of 47' TCH and typically is 50'.  Also, the TCH is now always published.  
If you fly a bigger jet you must know the difference in the wheel base height to altimeter at the TCH.  The jet I fly gives a lot of data in this area.
Also, consider these numbers.  One dot glideslope deviation at the OM = 50'.  One dot glideslope deviation at the MM = 8'.  
If, on a contaminated runway, at the MM I adjust my flight path to fly one dot below the glideslope...I will have at least a 42' TCH...and a much improved opportunity to land a few hundred feet earlier in the TDZ.  I know that as low as 25' TCH I should be okay as far as the wheels clearing the ALS.
FWIW, I don't like to call this a "duck under" maneuver.  To me the term "duck under" implies that I'm at a minimum altitude and I do not have sufficient visual references insight...and I'm busting an altitude to try to see something.  For example...being on G/S, below DH, without the necessary visual cues in sight...is a "duck under".  In my example...I have the necessary visual cues in sight...I'm adjusting my flight patch visually to achieve a certain touchdown objective.  If this adjustment entails a one dot glideslope deviation...I feel certain...knowing the feet of glideslope deviation and my wheel base height...that I'm safe as far as obstructions are concerned.  
Now, back to what Mr. Creepy said...on a slippery runway...I want to be down and braking...especially since my data says I should be on the ground 1000' from the landing threshold and braking.  I definitely think a slight adjustment of the flight path is good judgment to make this happen.  Typical landing data gives perfomance based on NO Flare.  To me this is unrealistic...as I've never seen anyone not flare an airplane under any situation.  It always adds least 500' if not more to a typical landing.
One other piece of info...I did not realize...my jet's contaminated landing performance is based on FULL Reverse Thrust.  I never new this before.
Jim,
FWIW, I appreciate the discussion on this topic, alot of it brought up by TonyC.  It's made me think about this issue a little deeper and reevaluate my understanding of the issues involved in changing the flight path after the MM.  All of us should realize the hazards present in landing data.  A maximum performance stop is something that a lot of professional pilots would be unable to acheive given the prerequisites set forth in the data.  Heck, even being within 1000' of minimum landing distance should have us employing what the typical line pilot would view as a maximum stopping effort.  As we all know, every winter, there are a handful of jets several hundred feet off the end of the runway.