Science Court: Past Proposals, Current Considerations, and a Suggested Structure

43 Pages Posted: 10 Mar 2010 Last revised: 20 Oct 2011

Date Written: March 1, 2010


The improper bending of scientific opinion by outside influences has been a concern of scholars and commentators for decades. The interference of outside influences with scientific analysis pushed Arthur Kantrowitz in 1967 to propose a procedure for making scientific assessment by non-scientists more objective. The perception of increasing partisan influence in the mid-1970’s led to a vigorous public debate of the Kantrowitz proposal. A critical question of that debate is equally important for the current judicial system: how long will we tolerate the partisan exploitation of scientific uncertainty?

This Article reviews Kantrowitz’s proposal, analyzes its criticisms, and discusses how it ultimately failed to change scientific evaluation methodology. After assessing legal changes that have occurred since Kantrowitz’s proposal, this Article proposes Congress should create a centralized Court of Scientific Jurisdiction to handle complex science and technology cases.

Ultimately, this Article shows that by incorporating expertise into the judiciary, the Court of Scientific Jurisdiction could objectively assess scientific and technological evidence, resulting in more reliable, predictable, and scientifically valid outcomes, without sacrificing due process and fairness.

Keywords: Daubert, gatekeeping, expert, science, technology, specialization

Suggested Citation

Jurs, Andrew W., Science Court: Past Proposals, Current Considerations, and a Suggested Structure (March 1, 2010). Virginia Journal of Law and Technology, Vol. 15, No. 1, 2010, Drake University Law School Research Paper No. 11-06, Available at SSRN:

Andrew W. Jurs (Contact Author)

Drake University Law School ( email )

2608 Forest Avenue
Des Moines, IA 50311
United States
515-271-2824 (Phone)

Do you have a job opening that you would like to promote on SSRN?

Paper statistics

Abstract Views
PlumX Metrics