bind variable peeking (also known as bind peeking), the optimizer looks at the value in a bind variable when the database performs a hard parse of a statement. The optimizer does not look at the bind variable values before every parse. Rather, the optimizer peeks only once when the optimizer is first invoked, which is during the hard parse.

Because the optimizer only peeks at the bind value only once during the hard parse, the plan may not be optimal for all possible bind values.

When a query uses literals, the optimizer can use the literal values to find the best plan. 

Three different plans with Literals

But if you use Bind then the first value is peeked and the same plan is used for the remaining ones. You will notice all plans are same as first one. For the value 113800 a FTS was more beneficial instead of INDEX range scan. solution to this is Adaptive cursor sharing (ACS)