Recurring loss of registered elevator destinations needs a documented service investigation, not an assumed programming fix. Record the car, timing, selected floors and visible status, then have the licensed elevator contractor correlate those observations with controller events and operating inputs.
When elevator calls disappear after an intermediate stop, report a recurring operating fault rather than assuming the dispatch program is wrong. The symptom alone cannot identify the cause. Call-cancellation settings, service modes, floor-access controls, position faults and indication problems can produce similar observations.
Your useful first step is to record which car was involved, what remained selected before the stop, and exactly when the indication changed. Leave controller checks, service-switch operation and diagnostic rides to the licensed elevator contractor. Do not reset the equipment before the contractor has had an opportunity to preserve its fault history.
Separate the symptoms before naming a cause
A car call is a destination selected inside the elevator. A hall call requests an elevator from a landing. Keeping those terms separate makes a fault report easier to interpret.
Record the visible sequence without turning it into a diagnosis:
- A destination button lights, then goes dark at an intermediate stop. This may indicate cancellation, but a lamp or panel communication problem can also change the indication. Note whether the destination is subsequently served.
- The button never lights or the selection is immediately rejected. This points toward a different investigation, such as floor access, panel input or the current operating mode.
- The remaining selection disappears as the doors open. The timing makes stop-related cancellation logic worth checking. It does not prove that the door detector is defective.
- The selection disappears as the doors close or travel resumes. Record that timing separately. A controller event, mode change or communication interruption could occur at that stage.
- The car returns to the lobby without serving the remaining destination. This confirms that the requested trip was not completed. It does not, by itself, distinguish normal parking after cancellation from recall or position recovery.
- Several selections or panel indicators disappear together. Note whether the floor indicator, lighting or other visible equipment also changes. A broader interruption needs different checks from one failed button lamp.
An extinguished button and an unserved destination together are more informative than either observation alone. Neither identifies a failed component without further evidence.
Decide whether the car needs immediate attention
Notify building management and the elevator contractor promptly when a registered destination is repeatedly dropped. Do not leave the condition as an undocumented inconvenience or ask normal traffic to reproduce it.
Escalate immediately if the event includes unexpected movement, an apparent mismatch between the car floor and landing, abnormal door behavior, unusual noise, smoke or a burning smell. Follow the building's established procedure for restricting use and obtaining emergency assistance. Do not enter restricted equipment spaces or improvise an isolation procedure.
If the car is occupied and cannot complete its trip, use the installed alarm or emergency communication system and follow the emergency response instructions. Do not force doors or attempt an exit between landings.
An active building alarm takes priority over this investigation. Follow the building emergency plan rather than using elevator travel to investigate the symptom.
Capture the evidence before it is lost
Give the contractor a short event record. The following details are useful even when no controller information is available:
- Car identification: the car label or number, not just the elevator bank or lobby location.
- Time: the date and the closest available timestamp, including whether it came from a clock, access record or another source.
- Trip sequence: starting floor, direction, selected destinations and the intermediate floor where the change occurred.
- Indication timing: whether the destination light changed before door opening, during the open-door period, during closing or after movement began.
- Actual service: which destinations were served, which were missed and where the car went next.
- Visible status: the floor indication, service messages and any unusual indicator lights. Record their wording rather than interpreting their meaning.
- Associated events: a building alarm, known power interruption, access restriction or scheduled service activity at the same time.
Separate observations from assumptions. “The upper-floor selection went dark while the doors were open” is useful evidence. “The car lost its position” is a hypothesis until the controller records support it.
Do not deliberately load many calls, obstruct the doorway or repeat rides to obtain a better report. Existing observations are enough to request a service investigation. Ask the contractor to preserve relevant logs before any reset that could erase or obscure them.
Understand the possible causes without testing them yourself
Several mechanisms deserve consideration. Their behavior depends on the installed controller, configuration and building interfaces.
| Possible cause | What could fit the symptom | What the contractor needs to establish |
|---|---|---|
| Anti-nuisance call cancellation | Remaining calls clear at a stop because the controller classifies them as unwanted | Whether that feature is enabled, what inputs it uses and whether those inputs match actual conditions |
| Special operating mode | Call acceptance or service order differs from normal operation | The documented mode, switch inputs and associated controller events |
| Floor-access control | Certain destinations are rejected or removed | Whether permissions, schedules or interface signals changed at the event time |
| Position or recovery fault | Calls are cleared and the car travels to a reference or recovery landing | Whether the fault history records position loss or a recovery sequence |
| Panel or communication fault | Button indications change or selections are not retained | Whether the controller received and retained the calls, and whether panel communication remained healthy |
| Recall or another external command | Normal service is interrupted and the car travels to a designated landing | Which command was active and whether its source was valid |
Some systems use door-related or load-related information in anti-nuisance decisions. That does not mean every door protective detector supplies occupancy information. A door detector's safety function and a controller's call-cancellation feature must not be treated as interchangeable.
Likewise, a service-mode label does not establish exactly how that installation accepts calls. Do not turn keyed switches to compare behavior. Fire-service indications and door behavior are evidence to report, not a safe basis for an informal operating-mode test.
Returning to the lobby is also not proof of position loss. The car might simply have no remaining registered calls and then respond to another demand or parking command.
Ask for a fault investigation, not a reset alone
The repair request should state the recurring symptom and ask the contractor to correlate it with controller and building-interface records.
The investigation should address:
- Whether the destination call was accepted, retained and later cancelled, or whether only its indication changed.
- The operating mode and external commands active at the recorded time.
- Relevant call-cancellation settings and the inputs those settings depend on.
- Position, door-zone, panel communication and power-related events where applicable.
- Floor-access and alarm-interface records when the timing makes them relevant.
- Whether the condition affects one car or several cars in the bank.
A problem confined to one car makes car-specific equipment worth examining. Similar events across several cars make shared inputs or settings worth examining. Neither pattern proves the cause, and a clean record from another car does not establish that the affected car has a hardware fault.
Do not request that anti-nuisance logic, access controls or a protective function simply be disabled. The appropriate fix is to identify an incorrect input, failed component, configuration error or documented software issue and correct it through the manufacturer's supported procedure.
Confirm the repair and communicate the status
Ask for a service report that identifies the cause, the corrective work and the checks used to confirm normal operation. “Reset and running” does not explain a recurring loss of registered calls.
The contractor should select and conduct any necessary diagnostic trips under controlled conditions. Where appropriate, those checks should include the reported intermediate-stop sequence, confirmation that remaining calls are retained and review of the relevant event history afterward. A successful trip alone does not explain an intermittent fault.
Building management should record the release-to-service decision and keep the original event details with the repair report. If the symptom returns, add a new timestamp and car identification rather than starting with an undocumented reset.
If a service notice is shown on an elevator information screen, keep it consistent with the actual car status. A notice communicates an outage or restriction; it does not replace the building's procedure for keeping an affected car out of use.
Questions
Does returning to the lobby mean the elevator lost its position?
Not necessarily. The call may have been cancelled, rejected by an operating mode or access rule, or affected by a panel communication problem. A position fault is another possibility, but the return trip alone does not prove it. Controller records must establish the sequence.
Should the elevator be reset when destination calls disappear?
Do not cycle power as an informal troubleshooting step. A reset can alter the state needed for diagnosis or affect stored evidence, depending on the equipment. Follow the building's fault-reporting procedure and let the licensed elevator contractor decide when a reset is appropriate.
What information should accompany the service request?
Record the car identification, date, approximate time, selected floors, intermediate stop and the moment the destination indication changed. Include the actual next destination and any visible service messages. Report observations without operating switches, obstructing doors or arranging repeated rides.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.