P0720 concerns the transmission output-speed sensor circuit; P0722 identifies a missing output-speed signal. Neither code, on its own, proves that the transmission's internal mechanical parts have failed. The first task is to establish whether the controller is receiving believable speed information and, if not, where that information is being lost.
The distinction matters when a vehicle shifts unexpectedly or a shop proposes a major transmission repair. Request the complete scan report and the evidence behind the recommendation before approving a sensor, leadframe, controller or transmission assembly.
Safety comes before reproducing the fault
Unexpected downshifts, severe or unpredictable shifting, loss of drive, or an unreliable speed indication make continued driving a poor diagnostic experiment. Stop safely and arrange professional assessment or recovery. Tell the recovery provider about the symptoms and follow the vehicle's specific transport requirements.
Do not attempt to reproduce a sudden downshift, watch live scan data while driving, or run the driven wheels with the vehicle supported on a jack. Do not bypass wiring to simulate a speed signal. Transmission work can involve hot fluid, moving components and vehicle-support hazards; this guide does not provide an under-vehicle repair procedure.
A restart that temporarily restores normal behavior does not establish that the fault is repaired. Preserve what happened rather than repeatedly resetting the vehicle to continue a trip.
What the controller is missing
Output-speed information describes rotation on the transmission's output side. It is different from the selector's Park, Reverse, Neutral or Drive position. That is why a range-signal code such as P0705 and an output-speed code are not interchangeable diagnoses.
Ford's 2010 gasoline OBD summary distinguishes P0720 circuit concerns from P0722 no-signal concerns. It also describes comparisons with other speed information, with different criteria for different transmissions. The important principle is that a speed reading must make sense in context, not merely show a number. Its thresholds are not universal test specifications. Ford OBD summary, page 184
Ask the shop which transmission is fitted and which sensor or signal the exact code refers to. Do not order a part solely from a generic scanner's abbreviated description.
Save the evidence before clearing
Ask for every relevant module's codes, including their status and any suffixes, plus available recorded operating data. State whether the complaint was a harsh shift, unexpected downshift, missing drive, warning message or speed-display problem. Describe observations already made; do not create another incident to collect evidence.
Include the timing of previous transmission, wiring or battery work and any earlier sensor replacement. An invoice showing what was installed can prevent another shop from assuming the original component remains in place. A repair history is a clue, not automatic proof that the previous repair caused the current fault.
If the vehicle behaves normally during the appointment, ask the technician to distinguish what was confirmed from what remains suspected. An intermittent signal loss may require more investigation than a code scan alone.
Wiring checks belong before a controller verdict
Mitsubishi's cited 2018 P0720 procedure considers the output-speed sensor, connectors, harness and transmission controller. Its diagnostic sequence checks the electrical paths and signal before reaching controller replacement. It also uses other transmission information as prerequisites for its monitoring. This is an application-specific example of checking the evidence chain, not a universal connector test. Mitsubishi P0720 diagnostic information
Ask which signal was absent or implausible and whether testing located the fault at the sensor, its supply or wiring, or the receiving end. “The code says speed sensor” does not answer those questions. The report should explain why the proposed part is the failed part rather than simply the component named in the code.
The Ford leadframe example has important limits
Ford's April 2019 customer satisfaction program 19N01 addressed specified 2011–2013 F-150 and 2012–2013 Expedition/Navigator vehicles with the 6R80 transmission. It described output-shaft-speed sensor failure with selected codes, including P0720 and P0722, and a molded leadframe repair for the covered condition. Ford program 19N01
This was not a direction to replace every affected transmission. It also referenced separate software programs and required the relevant history to be addressed before proceeding. The published coverage had time and mileage limits. Do not read the old no-charge wording as a current promise of free repair, or assume an unrelated Ford transmission uses the same fix.
Ask a dealer to check the VIN, transmission, symptom and campaign history against current information. A customer satisfaction program and a safety recall are not the same thing; have any applicable open recalls checked separately. Coverage and diagnosis are separate questions, and an expired program does not explain away a current fault.
P0716 and P0717: the input-speed target can matter too
Input/turbine-speed faults concern different information from output-speed faults. In Ford's 2011 OBD summary, an input-speed monitor distinguishes erratic signal P0716 from missing signal P0717. The exact transmission determines the monitoring and diagnostic path.
A sensor-named fault can also have a mechanical explanation. GM bulletin 16-NA-013, January 2016 covers listed 2016 applications with specified transmissions, including Enclave and Traverse. It describes no Reverse, sometimes no third gear, erratic input speed and active or historical P0716/P0717. An out-of-position retainer for the rotating sensor target can cause that condition.
The specified repair includes the retainer, target wheel and associated clutch piston/housing components, with other damaged parts assessed as needed. It is not merely an electrical-sensor replacement, nor proof that every vehicle with either code needs an entire transmission.
Ask what supports a circuit fault versus a problem with the mechanical target, and how the already-observed missing-gear pattern fits the diagnosis. Match the exact transmission and current service information before applying this example. Do not drive to identify missing gears or attempt internal inspection; unsafe engagement or shifting retains the stop-and-recovery guidance above.
Questions before an expensive authorization
For a sensor or leadframe proposal, ask what ties the observed signal loss to that component on your transmission. For wiring work, request the location and nature of the fault. For a controller, ask what tests excluded the inputs and circuits it depends on.
If a complete transmission is recommended, request the additional mechanical findings that justify it beyond these codes. A signal fault and a mechanical fault can coexist, but that possibility is not evidence that both are present. Ask for an itemized explanation separating confirmed repairs from optional or speculative work.
What should be verified afterward
Request documentation of the relevant speed information, operation of the affected functions and final scan findings under the manufacturer's verification procedure. The warning being erased is not sufficient by itself. If the problem was intermittent, ask what was actually verified and what to report if it returns.
Keep the initial scan, diagnostic findings and repair invoice together. That creates a useful comparison if the same symptoms recur and helps avoid another round of guessing from the code alone.
Frequently asked questions
Does no signal mean the shaft stopped rotating?
Not necessarily. P0722 describes missing speed information to the controller. The diagnostic task is to determine why that information is missing, using the correct vehicle procedure.
Can a transmission-fluid change fix these codes?
Do not authorize a fluid service solely as a cure for an unproven electrical signal fault. Maintenance and fault diagnosis are different decisions.
Is every speedometer problem P0720 or P0722?
No. A speed-display complaint needs its own evidence and system identification. Do not infer a particular sensor from the dashboard symptom alone.