563 P.3d 136
Ariz.2025Background
- Mother initiated adoption proceedings for her unborn child, M.N., identifying her boyfriend (not the biological father) as the father and omitting Delvagus I. (“Father”).
- Upon learning of Father’s existence, the adoption agency served him with notice under A.R.S. § 8-106(G), triggering a thirty-day period for him to assert his rights by filing a paternity action.
- Father filed a paternity action, and genetic testing established him as M.N.’s biological father.
- The adoption agency argued for termination of Father’s parental rights primarily for failing to register as a putative father under § 8-106.01, despite his compliance with § 8-106(G).
- The juvenile court terminated Father’s rights; the court of appeals reversed, leading to review by the Arizona Supreme Court regarding whether a noticed potential father must also file with the putative fathers registry.
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Must a potential father served with § 8-106(G) notice file with the putative fathers registry under § 8-106.01? | Choices: All potential fathers must also register as putative fathers to protect their rights; non-registration is grounds for termination. | Father: Once noticed as a potential father and compliance with § 8-106(G), registry filing is unnecessary. | No, a served potential father need not register; failure to do so is not grounds for termination. |
| Are potential and putative fathers distinct legal classifications? | Choices: Overlap exists and failure to comply with either process can result in termination. | Father: Statutes address separate classes, with different requirements and rights. | They are distinct; each with different statutory requirements and termination grounds. |
| Does requiring both notice and registry filing violate due process or legislative intent? | Choices: Legislative intent was to safeguard adoption proceedings by requiring both steps. | Father: Imposing both steps is duplicative, creates traps, and is not supported by statutory language. | Imposing both is contrary to legislative intent and due process; statutes work independently. |
| Did the juvenile court err in terminating Father’s parental rights? | Choices: Court correctly applied the putative father registry requirement. | Father: Court erred because he fulfilled all potential father requirements. | Yes, termination on these grounds was improper; reversed. |
Key Cases Cited
- Frank R. v. Mother Goose Adoptions, 243 Ariz. 111 (Ariz. 2017) (Discusses putative father registry as a ground for termination, clarifies it does not apply to every father)
- David C. v. Alexis S., 240 Ariz. 53 (Ariz. 2016) (Clarifies distinction and notice requirements for potential vs. putative fathers)
- In re Drummond, 543 P.3d 1022 (Ariz. 2024) (Principles of statutory interpretation for parental termination statutes)
- Santosky v. Kramer, 455 U.S. 745 (U.S. 1982) (Parental rights are fundamental and subject to strict scrutiny)
- Troxel v. Granville, 530 U.S. 57 (U.S. 2000) (Affirms fundamental right of parents in child-rearing)