Date: 201603
Local time of day: 1801-2400
Location: OGG.Airport, HI
Flight conditions: VMC
Light: Night
Aircraft: Airbus Industrie Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class C OGG
ATC / advisory: Tower OGG
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: I was the Captain and pilot flying on flight to OGG. Following a routine flight to OGG; the destination weather was 6+ miles visibility; 6000 broken cloud layer; winds variable. We were vectored for an ILS/Visual to runway 2. I hand flew a stable approach and experienced a wind shift from a left crosswind to a direct tailwind just prior to landing. As a result; I touched down a little longer than my aiming point of 1000 ft and just prior to main wheel contact the ROPS (Runway Overrun Prevention System) alerted; 'Runway Too Short'. I was aware of my position on the runway and knew that there was plenty of runway to continue the landing and slow the aircraft to taxi speed well prior to the end of runway as opposed to executing a G/A. I have been flying into OGG for the last 4 years and had a lot of experience with the OGG airport and its uniqueness. I also have over 3200 hours on the Airbus and felt that the safety of flight was never in question. Following the touchdown I used full reverse and moderate braking which ensured we had plenty of remaining runway. We cleared the runway and taxied to the gate without incident. Once on the gate the F/O and I discussed the event and he also felt that although we did receive the ROPS alert; there was never any doubt to the safe operation of the aircraft.This event serves as a constant reminder that we as pilots operate in an ever changing environment and each and every flight requires we perform to the best of our abilities. Because this event took place on such short final; just prior to touchdown; there was not a lot of time to discuss what I felt was the best option with the F/O. I did; however; feel I was always operating the aircraft in a very safe manner and never had a doubt to the safe outcome of my actions. Had the ROPS provided the same alert farther out on the approach; I would [have] executed a G/A not knowing what changing dynamics might cause this alert on a stable approach.


Second narrative: Just prior to touchdown we received a 'runway too short warning' from the ROPS system. This warning was a surprise to me as we were very close to the pavement and appeared to be within the touchdown zone. As pilot monitoring I probably should have called for a go around in this situation. The approach had been stable [so] the warning was unexpected by me. Perhaps a mention of a ROPS system warning in the approach briefing; similar to how many Captains brief wind shear warnings in the takeoff briefing; would be a good idea in some situations.


Synopsis: Airbus flight crew reported receiving a 'runway too short' alert from the ROPS; but they were near touchdown and ignored it.