Who was Achan's father?

What follows is one scholar’s way of reading this disagreement — a critical-historical view that often concludes the texts genuinely disagree. It draws on the peer-reviewed sources listed below and stands as one position among the answers above, presented for transparency, not as GEBible’s position.

How critical scholarship weighs this: Usually considered reconciled

This summarizes where critical scholarship tends to land on this tension — a report on the field’s center of gravity, not GEBible’s own ruling.

This entry sits at the weak end of the contradiction spectrum and is essentially resolved by ordinary Hebrew lexicography. Joshua 7:1 gives Achan a four-generation pedigree: "Achan, the son of Carmi, the son of Zabdi, the son of Zerah, of the tribe of Judah." Joshua 7:24 and 22:20 then call him "Achan the son of Zerah" directly, collapsing the chain to a single father-son pairing. The parallel at 1 Chronicles 2:7 names him "Achar, the son of Carmi" — note the variant spelling — confirming Carmi as the immediate father and Zerah as the more distant clan ancestor.

The harmonization is the standard flexibility of Hebrew *ben*, "son of." The term regularly denotes a descendant rather than strictly an immediate son, a usage documented across the standard reference works: BDB and HALOT both list "descendant" among the core senses, and the grammars of Waltke-O'Connor and Joüon-Muraoka note the genealogical elasticity of *ben* in pedigree formulas. The biblical examples are numerous and uncontroversial: Jesus is "son of David" across centuries (Matthew 1:1); Jehu is called "son of Nimshi" (1 Kings 19:16) though Nimshi was his grandfather and Jehoshaphat his father (2 Kings 9:2); Laban is "son of Nahor" (Genesis 29:5) when Bethuel was his father. Calling Achan "son of Zerah" identifies him by his prominent eponymous clan ancestor — Zerah being the head of a major Judahite clan (the Zerahites, Numbers 26:20) — exactly as Joshua 7:1 specifies in full. There is no collision; the short and long forms are two levels of the same genealogy. This is a genuine harmonization, not a salvage operation, and the entry is best rated harmonized.

It is worth noting that the variation is unsurprising in narrative practice. A formal genealogical introduction (Joshua 7:1) supplies the full lineage to establish the offender's tribal and clan identity for the *ḥērem* episode; the subsequent narrative references (7:24; 22:20) use the convenient shorthand of the well-known clan ancestor. The pattern of full-pedigree-then-shorthand is widespread in Hebrew narrative and signals nothing anomalous.

The one observation a critical reader may add is text-historical rather than contradictory. The name itself varies — Joshua reads Achan (*'ākān*), Chronicles reads Achar (*'ākār*), and the narrative in Joshua 7:25-26 puns on the Valley of Achor (*'ākôr*, "trouble"), since Achan "troubled" Israel. The Achar/Achor wordplay suggests the tradition was shaped by an etiology for the valley's name, and Robert Boling and J. Alberto Soggin note redactional development in the Achan narrative, including the slotting of clan-genealogical material into a shorter original story. But that observation concerns the literary growth of the episode, not a genealogical contradiction; the "son of Zerah" phrasing remains fully consistent with the four-generation pedigree under normal Hebrew usage.

The verdict is straightforward: this is an overstated contradiction, resolved by the well-attested descendant-sense of *ben*. The mild unevenness between full and short forms may hint at the episode's compositional history, but it does not generate a factual conflict about Achan's paternity. The entry is a reasonable candidate for downgrade or deletion from a list of substantive contradictions.

Where the critical reading lands: harmonizable; resolved by standard Hebrew lexicography.