How Can Two Inerrant Scriptures Differ Over a Common Historical Fact?

In this episode, Dr. E answers a challenging question about the timeline of Jesus’ crucifixion. From the “sign of Jonah” to the apparent differences between the Synoptic Gospels and John, Dr. Easley walks through how to understand these passages in their proper historical and cultural context. What about the “three days and three nights”? Did Jesus celebrate Passover before or after His arrest? And if the accounts don’t line up perfectly, can we still trust the Bible? Dr. Easley explains how ancient Jewish idioms, feast practices, and eyewitness perspectives help resolve these tensions. Rather than weakening Scripture, these differences actually strengthen its credibility and reliability. If you’ve ever wrestled with questions about Gospel contradictions, biblical inerrancy, or the accuracy of Jesus’ resurrection timeline, this episode will give you clarity and confidence in God’s Word. Key Topics Covered -The “sign of Jonah” and what Jesus meant by three days and three nights -Why a 72-hour timeline isn’t required for the resurrection -Differences between the Synoptic Gospels and John -The Passover timeline and Jesus’ final meal -Jewish idioms and how they affect biblical interpretation -What biblical inerrancy really means -Why Gospel differences strengthen, not weaken, credibility -How oral tradition preserved the accounts of Jesus Chapters 00:00 What About Gospel Contradictions? 01:05 The “Sign of Jonah” Explained 02:30 Do Three Days Mean 72 Hours? 04:00 Understanding Jewish Time Language 05:40 The Passover Timeline Problem 07:00 Synoptic Gospels vs. John 08:30 Did Jesus Eat the Passover Meal? 10:00 Why the Accounts Differ 11:30 What Is Biblical Inerrancy? 13:00 Do Differences Undermine Scripture? 14:30 Why the Bible Is Still Reliable 16:00 Final Thoughts & Encouragement Links Mentioned: The Diary of a CEO Find more episodes of Ask Dr. E here. If you've got a question for Dr. Easley, call or text us your question at 615-281-9694 or email at [email protected].