oracle performance on date range query
The reason is that the cost-based optimizer has a plan in memory from a previous select, where the number of records for a given organization, namely 'LOL', was much smaller, some 14000.  When the plan is in memory, the CBO doesn't care about the parameter values anymore.  Use:

WHERE organization || '' = 'BA'